-
Notifications
You must be signed in to change notification settings - Fork 6
Creating a new branch
Branches are where we make changes to a specific part of the website before committing the changes to dev. These are the steps you need to take to create and commit branches in Github before preparing a pull request.
-
Open Github Desktop and set the current repository to the one you are updating.
-
Set the current branch to dev.
-
Pull origin. You can do this by either hitting the Pull Origin button or clicking the down arrow next to Pull Origin. The button and the down arrow will only display if there are commits in dev that you don’t currently have on your machine. If there is anything available for you to click on that says pull origin – do it before proceeding.
-
Create a new branch by opening the current branch menu and hitting ‘New branch.’
-
Enter a branch name into the text box, then hit Create branch. Make sure your branch name is brief and explains what it’s for. The name is case sensitive and is what will go into the preview URL for the pull request.
-
With the new branch open in Github Desktop, open Atom on your machine. Go to File-Open Folder and Select the repository you are working with.
-
Make sure the lower left corner is set to your branch. It should show your branch name and if you have pulled origin before opened Atom, there should be no number or pulls listed. It should just say Fetch. If it shows something other than the branch you just created, click on the branch name and choose yours from the drop down.
-
Make your changes in Atom and save.
-
Return to Github Desktop. Your changes will be listed on the left. Make sure that the boxes next to all your changes are checked.
-
Enter the summary. No need to add a description, but make the summary detailed enough so that someone else looking at this commit knows what to look for.
-
Hit the blue “Commit to [branch name]” button.
-
Now the Publish Branch button will display in Github. Use that to initiate creating a pull request and follow the instructions on the How to prepare and review pull requests page.
- Problem statement
- Product vision
- User scenarios
- What we're not trying to do
- Product risks
- Prioritization scale
- Technical overview
- Contributing to code
- Creating a new branch
- How to prepare and review PRs
- Releasing changes
- Database change management
- Tech Solutions
- Data overview
- How to upload monthly data
- How to upload OGOR-B Data
- Troubleshooting for specific datasets
- Goals and metrics
- Analytics
- DAP-GA4 templates & instructions
- DAP-UA templates & instructions
- User research plans & findings
- Joining the team
- Onboarding checklist
- Working as a distributed team
- Planning and organizing our work
- Sample retro doc
- Human centered design process
- User research study process
- Design Standards
- Usability testing process
- User research participant guide
- User research agreement
- Observing user research
- Design and research in the federal government
- Shaping process
- Research wiki
- Data catalog
- Problem statement (2016)
- Hypotheses (2016)
- Outcomes workshop (2017)
- Transition goals (2018)
- Product management training (2018)
- Information architecture
- NRRD-flavored Markdown (Jekyll site)
For information about our other website see our ONRR.gov wiki.