newdevs:git:create
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
newdevs:git:create [2019/06/28 17:06] – tmccanna | newdevs:git:create [2024/02/01 10:46] – [3. Make Your Changes] tmccanna | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | **New Developers Working Group** | ||
====== Git for Windows ====== | ====== Git for Windows ====== | ||
- | ===== Using Git to Create | + | ===== Using Git to Create |
+ | When you make code changes that you wish to post for review, you will create a git branch to store them in. | ||
==== 1. Update Your Local Repository ==== | ==== 1. Update Your Local Repository ==== | ||
Line 8: | 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 |
</ | </ | ||
+ | |||
+ | Note: Depending on how Git is configured on your machine, you may just be able to enter: git pull | ||
+ | |||
==== 2. Create a New Branch to Store Your Changes ==== | ==== 2. Create a New Branch to Store Your Changes ==== | ||
- | Create and checkout a branch to store your changes. | + | Create and checkout a branch to store your changes. |
<code bash> | <code bash> | ||
- | git checkout -b user/username/ | + | git checkout -b lp123456_launchpad_bug_description |
+ | </code> | ||
+ | |||
+ | 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 | ||
+ | </code> | ||
+ | |||
+ | 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 | ||
</ | </ | ||
==== 3. Make Your Changes ==== | ==== 3. Make Your Changes ==== | ||
+ | |||
- Edit the file(s) you wish to change. You can either do this by launching a text editor from within Git Bash (notepad++ filename.tt2) or you can do so by opening and editing the file from Windows Explorer. | - Edit the file(s) you wish to change. You can either do this by launching a text editor from within Git Bash (notepad++ filename.tt2) or you can do so by opening and editing the file from Windows Explorer. | ||
- Verify that Git recognizes the files you have modified: git status | - Verify that Git recognizes the files you have modified: git status | ||
- Add the file(s) you have changed to the staging area: | - Add the file(s) you have changed to the staging area: | ||
- | * To stage a specific file, use: git add myfilename.txt | + | * To stage a specific file, use: **git add myfilename.txt** |
* 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 38: | 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: | ||
- | |||
- | |||
==== 4. Push Your Changes to the Evergreen Working Repo ==== | ==== 4. Push Your Changes to the Evergreen Working Repo ==== | ||
- | Upload | + | In order to share your branch, you will need to upload |
<code bash> | <code bash> | ||
- | git push working user/username/ | + | git push working |
</ | </ | ||
newdevs/git/create.txt · Last modified: 2024/03/12 15:10 by tmccanna