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 [2019/07/29 10:34] – [3. Make Your Changes] tmccanna | newdevs:git:create [2024/03/12 15:10] (current) – tmccanna | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | **New Developers Working Group** | ||
====== Git for Windows ====== | ====== Git for Windows ====== | ||
Line 9: | Line 10: | ||
- Open Git Bash | - Open Git Bash | ||
- Navigate into your Evergreen repository | - Navigate into your Evergreen repository | ||
- | - If the master | + | - If the main branch isn't currently checked out, check it out: git checkout |
- Before making any changes, make sure your local files are up to date with latest changes: | - Before making any changes, make sure your local files are up to date with latest changes: | ||
<code bash> | <code bash> | ||
- | git pull origin | + | git pull origin |
</ | </ | ||
Line 22: | Line 23: | ||
<code bash> | <code bash> | ||
+ | git checkout -b lp123456_launchpad_bug_description | ||
+ | </ | ||
+ | |||
+ | Note: In most cases you will want to create a branch based off of main. You can do this either by a) specifying main on the command line: | ||
+ | |||
+ | <code bash> | ||
+ | git checkout -b lp123456_launchpad_bug_description main | ||
+ | </ | ||
+ | |||
+ | Or, b) you can switch to main first and then create the new branch. This also gives you the opportunity to make sure your local copy of main is updated first: | ||
+ | |||
+ | <code bash> | ||
+ | git checkout main | ||
+ | git pull origin main | ||
git checkout -b lp123456_launchpad_bug_description | git checkout -b lp123456_launchpad_bug_description | ||
</ | </ | ||
Line 33: | 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 | ||
- | - Commit the staged changes: **git commit** | + | |
- | - When your text editor opens to write the commit message, the first line should be the launchpad number and name, followed by the description, | + | * https:// |
+ | | ||
+ | * 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 | ||
LP#1406387 Fix for Holds Placement Advanced Options | LP#1406387 Fix for Holds Placement Advanced Options | ||
Line 43: | Line 61: | ||
empty, regardless of whether the radio input for the | empty, regardless of whether the radio input for the | ||
hold was specified for a patron or the staff member. | hold was specified for a patron or the staff member. | ||
+ | | ||
+ | To reproduce the problem: | ||
+ | [1] Open a patron' | ||
+ | [2] On the hold placement screen, click Advanced Hold options. | ||
+ | [3] You will see that the staff barcode is filled in rather than the patron. | ||
+ | | ||
+ | To test the fix: | ||
+ | [1] Open a patron' | ||
+ | [2] On the hold placement screen, click Advanced Hold options. | ||
+ | [3] Verify that the patron barcode is filled in. | ||
+ | [4] Test placing a hold directly from the catalog and confirm that the | ||
+ | staff or patron barcode is carried over from the main hold page. | ||
+ | | ||
+ | Release-note: | ||
| | ||
Signed-off-by: | Signed-off-by: |
newdevs/git/create.1564410856.txt.gz · Last modified: 2022/02/10 13:34 (external edit)