Skip to content

docs: [TESIS-000] require full real timestamps for new migrations #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TomasMartin2004 merged 2 commits into from
Sep 26, 2026
Merged

docs: [TESIS-000] require full real timestamps for new migrations #92

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
05bc3fb
docs: require full real timestamps for new migrations
LauAubert Sep 26, 2026
b07653b
Merge branch 'master' into TESIS-000-migration-timestamp-rule
TomasMartin2004 Sep 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,19 @@ El sistema implementa **row-level multi-tenancy**: todas las empresas comparten

#### 1. Migración

> **Regla obligatoria — timestamp completo y real.** Toda migración nueva se genera con
> `bin/rails generate migration NombreDeLaMigracion`, que usa la fecha y hora actuales
> (`YYYYMMDDHHMMSS`, con segundos). **Nunca** escribas el timestamp a mano ni uses valores
> redondeados como `...120000` o `...000000`: dos personas (o agentes) trabajando en ramas
> distintas eligen el mismo número, Rails falla con `DuplicateMigrationVersionError` o, peor,
> una migración queda marcada como corrida sin haberse aplicado.
>
> Si creás el archivo sin el generador, tomá el timestamp de `date -u +%Y%m%d%H%M%S`.
> Antes de pushear, verificá que no haya versiones duplicadas contra `master`:
> `ls db/migrate | cut -c1-14 | sort | uniq -d` (tiene que salir vacío).
> No renombres migraciones que ya están en `master`: cambiarles la versión hace que se
> vuelvan a correr en las bases donde ya se aplicaron.

```ruby
# db/migrate/YYYYMMDDHHMMSS_create_products.rb
class CreateProducts < ActiveRecord::Migration[8.1]
Expand Down
Loading