0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-12-23 22:20:43 -05:00
Forgejo Documentation https://forgejo.org/docs/
Find a file
Earl Warren ab0782c39c
docs: developer: workflow: requirement for Forgejo database migrations
While feature branches may have different requirements for the Forgejo
tables, they are constrained by the migration logic that requires they
happen in sequence and are listed in the same list. If each feature
branch changes the `forgejo_migrations/migrate.go` file independently,
it is bound to conflict with other feature branches trying to do the
same.

To avoid this situation it is proposed that once a migration
developped and tested in a freature branch is final, it is isolated in
a commit and moved to the `forgejo-development` branch. This can
happen during a rebase or with a pull request.

It is probably better that all migrations are ultimately squashed in a
single commit in the `forgejo-development` branch instead of an ever
growing list of commits. But this is up to the person in charge of the
migrations and since the directory is owned by forgejo, there is no
risk of conflict.
2023-08-13 17:10:14 +01:00
_images/user docs: user: profile: document user custom profiles 2023-08-13 16:36:21 +01:00
admin docs: admin: storage: create a new section 2023-08-13 17:10:14 +01:00
developer docs: developer: workflow: requirement for Forgejo database migrations 2023-08-13 17:10:14 +01:00
user fix: remove h1-level headings in docs 2023-08-13 17:08:33 +01:00
index.md refactor: use astro content collections for docs 2023-08-13 17:07:06 +01:00
license.md refactor: use astro content collections for docs 2023-08-13 17:07:06 +01:00