newdevs:git:create
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| newdevs:git:create [2024/02/01 10:39] – [3. Make Your Changes] tmccanna | newdevs:git:create [2024/03/12 15:10] (current) – tmccanna | ||
|---|---|---|---|
| Line 48: | Line 48: | ||
| * To stage //all// changed files, use: git add -A | * To stage //all// changed files, use: git add -A | ||
| * If you accidentally stage a file you didn't mean to, you can unstage it: git reset HEAD myfilename.txt | * If you accidentally stage a file you didn't mean to, you can unstage it: git reset HEAD myfilename.txt | ||
| + | - If you are adding a new feature (as opposed to a bug fix), you will also need to create a release note file. Look in the RELEASE_NOTES_NEXT folder for a template and examples: | ||
| + | * https:// | ||
| - Commit the staged changes: **git commit -s** | - Commit the staged changes: **git commit -s** | ||
| * Note: The -s portion adds the sign-off line for you. | * Note: The -s portion adds the sign-off line for you. | ||
| - | - When your text editor opens to write the commit message, the first line should be the launchpad number and name, followed by the description (with test instructions if relevant), then a brief release note line, and then followed by your sign off. For example: | + | - When your text editor opens to write the commit message, the first line should be the launchpad number and name, followed by the description (with test instructions if relevant), then a brief release note line (written in present tense), and then followed by your sign off. For example: |
| LP#1406387 Fix for Holds Placement Advanced Options | LP#1406387 Fix for Holds Placement Advanced Options | ||
newdevs/git/create.1706801953.txt.gz · Last modified: 2024/02/01 10:39 by tmccanna