package:dev:start
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
package:dev:start [2022/11/28 16:45] – created robert | package:dev:start [2022/11/28 17:19] (current) – robert | ||
---|---|---|---|
Line 53: | Line 53: | ||
git fetch github | git fetch github | ||
+ | |||
+ | == Giving other People Access to your Private Repo == | ||
+ | In Gitlab, on the main page of your private repository, go to " | ||
+ | |||
+ | == Creating a new Branch == | ||
+ | A new project or feature should, if possible, be started directly from the upstream main branch: | ||
+ | - git checkout main | ||
+ | - git pull | ||
+ | - git branch new_branch_name | ||
+ | - git checkout new_branch_name | ||
+ | |||
+ | == Updating from the Upstream Repo == | ||
+ | If you want to get the newest changes from the upstream repo into your current branch, you can: | ||
+ | - fetch the private repository: git fetch origin | ||
+ | - merge the changes into your current branch with: git merge origin/main | ||
== Pushing to the GitHub Fork == | == Pushing to the GitHub Fork == | ||
- | To be able to create a pull request your work first has to be publically available in your GitHub fork repo. Assuming that you have a branch named " | + | To be able to create a pull request, your work first has to be publically available in your GitHub fork repo. Assuming that you have a branch named " |
git push github new_work | git push github new_work |
package/dev/start.1669653945.txt.gz · Last modified: 2022/11/28 16:45 by robert