dev:committing
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
dev:committing [2023/11/08 08:35] – created sandbergja | dev:committing [2023/11/09 18:30] (current) – [Committing patches with database upgrade scripts] clarification about backporting sandbergja | ||
---|---|---|---|
Line 10: | Line 10: | ||
- Edit the upgrade script to make sure there is an uncommented evergreen.upgrade_deps_block_check line with the upgrade script number. | - Edit the upgrade script to make sure there is an uncommented evergreen.upgrade_deps_block_check line with the upgrade script number. | ||
- Change the file name of the upgrade script to start with the number. | - Change the file name of the upgrade script to start with the number. | ||
- | - In 002.schema.config.sql, | + | - In 002.schema.config.sql, |
- Commit the upgrade script and 002.schema.config.sql changes, using a commit message like "Stamp upgrade script" | - Commit the upgrade script and 002.schema.config.sql changes, using a commit message like "Stamp upgrade script" | ||
+ | |||
+ | If backporting the upgrade script to a release branch, use the same sequence number as you did in the main branch. For example, if you commit an upgrade script number 1234 to main, it should also be numbered 1234 in release branches. |
dev/committing.txt · Last modified: 2023/11/09 18:30 by sandbergja