![]() In particular, git has no concept of directly ![]() If you want to work with the changes in that remote branch, you must Made the branch and description is some free-form shortĭescription (and can include further slashes). U/user/description, where user is the name of the user who Trac tickets that are finished or in the process of being worked onĬan have a git branch attached to them. Look at the log, especially if the patch buildbot did not give you See trac ticket #wiki/patchbotįor more information about its features and limitations. The Patch buildbot will automatically test your ticket. Origin (fetch) origin (push) trac :sage.git (fetch) trac :sage.git (push) sage]$ git remote add trac :sage.git -t master If you want to use ssh only for both fetch and push, use the However, this configuration is not recommended if Using HTTPS from a mirror of the trac repository instead. The above instructions set up the remote to perform read-only operations ( fetch) Key as described in Trac authentication through ssh.Īuthentication is necessary if you want to upload anything to ensure Note that write operations ( push) use the ssh protocol (specified by the For this to work, you need to have a trac account and to set up your ssh public See theĬhecking Out Tickets section for examples. Tell git which branch you want to get from trac. But it also means that you will not fetchĮverything that is on trac by default, and you need to explicitly This avoids clutter by not automatically downloading allīranches ever created. Master branch on the trac server (the -t master In the command above we set up the remote to only track the Issuing some basic gitolite commands, for example: You can test that you are being authenticated correctly by It is only used to authenticate you to the gitolite installation on Note that this does not allow you to ssh into any account on trac, Paste the content of your public key file You can upload it in the preferences, that is , the Sage trac server needs to know your public In order to push your code directly to a branch on the git repository Linking your Public Key to your Trac Account # Passphrase empty to be able to login without any human intervention. Trust your own computer or system administrator, you can leave the The ssh-keygen tool will let you generate a key with a differentįile name, or protect it with a passphrase. ![]() This will generate a new random private RSA key Your public key has been saved in /home/user/.ssh/id_rsa.pub. Enter file in which to save the key (/home/user/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/user/.ssh/id_rsa. Using the following command, we can see which remote repository or repositoriesĪre associated with this local repository: In either case, this source directory is actually the main worktree of Obtained either from a source tarball or by cloning a Sage git repository In the following, we assume that you are in the source directory of Sage ( SAGE_ROOT), So that your changes can be reviewed for inclusion in Sage. We discuss how to push your local changes to a remote repository Now we continue our introduction to git from Sage Development Process. See our transition guide from Trac toįor the preliminary version of the workflow. Updated according to the new workflow on GitHub. Sage Trac server) will become obsolete and be The transition, some parts of this guide (especially those related with the Sage development is scheduled to move to GitHub in February 2023.
0 Comments
Leave a Reply. |