It’s always best to leave the repository name as “Marlin” unless you plan to make your own custom version of Marlin for publication. If it still hasn’t finished after few minutes then GitHub might be hung up (not unusual). You may need to wait for the Fetching Latest Commit message to go away also. This takes about 10-20 seconds, so be patient. When GitHub is done copying files, a page will appear displaying your shiny new fork of Marlin. Please upload a unique icon or image so it will be easier to identify you on the project pages! You’ll also need to download and install the GitHub Desktop application.Īfter signing in to your GitHub account, go to the main Marlin repository at: and create a fork of Marlin by clicking the fork icon in the top right of the page. Set up GitHub, Fork, and Cloneīefore you can contribute to Marlin, you need to get a free account. Following our guidelines ensures that your changes will be accepted more quickly. GitHub adds helpful collaboration features that make it an ideal platform for maintaining the Marlin project.īefore submitting code and other content, please review Contributing to Marlin and Marlin Coding Standards. Git will be familiar if you’ve used other version control systems like CVS, Apache Subversion, or Mercurial. The power of GitHub comes from the Git version control system. GitHub is a great tool for collaboration, but it has a bit of a learning curve. Do you wish to copy them to your repository?'.Contributing Code with Pull Requests Introduction Perhaps a dialog that says 'The following branches have been found on the upstream and not in the origin. I have used this command to do just that (although it just does every branch it finds) for branch in $(git ls-remote -heads upstream|sed 's#^.*refs/heads/#') do git push origin refs/remotes/upstream/$branch:refs/heads/$branch done found here. Offer a feature to selectively copy new upstream branches into the origin where a branch exists in the upstream but not the origin.If an upstream remote exists, on selecting a branch and before checkout, the user should be asked if the local branch should track the upstream or a branch on origin be created (if it does not exist) to track.It should be obvious which branch a branch is tracking (might be different names).Question - When selecting an upstream or origin branch, does git need to create a local branch or is this just a Desktop thing? I can checkout an upstream branch from the command line but Desktop then shows as detatched HEAD.Once a branch has been selected (say upstream/stable) if the branch with the same name in the other repo is selected (say origin/stable), the user just gets an error which is rather confusing.When a origin/ or upstream/ branch is selected, a local branch is created (checked out), but there is then no way of subsequently knowing which repository/branch it is tracking (origin or upstream) - what if there are more than 2 remotes? (using git branch -vv -a I can see that local branches are being created). In addition, that branch is no longer listed under origin or upstream which is rather confusing as the user knows it is there! That prefix just suddenly disappears after it is selected (checked out). When in the origin repository (my fork), or any repository for that matter, it is not immediately obvious (to a new user?) that a branch without either a origin/ or upstream/ before the name is a local branch.Someone creates a new branch on the upstream - I want to bring that branch into my fork. If I want to contribute to an upstream project I am not a formal contributor to, the simplest way is to create a fork (origin) clone that locally, create a working branch, then push that branch/changes to origin and create a PR to the upstream from there. Please describe the problem you think should be solved Bring new branches on upstream into origin Background
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |