How does regro-cf-autotick-bot create automatic version updates? ¶ Using Github’s hub tool (which conda-forge ships! conda install hub -c conda-forge):Ĭlone the conda-forge feedstock repositoryĬheckout the correct branch with remote: hub pr checkout 12 where 12 is the ID of the PR.Ĭommit and push on this branch, the remote is automatically set up to push to regro-cf-autotick-bot’s fork. If there are multiple remotes with this branch name, you need to first checkout the remote branch and then turn it into a local branch: git checkout regro-cf-autotick-bot/ & git checkout -b Ĭommit and push on that branch, if the remote was not correctly setup, use git push -u regro-cf-autotick-bot. ![]() ![]() See Which remote URL should I use?įor instructions on using the protocol if you haveįetch the remote: git fetch regro-cf-autotick-botĬheckout the branch of the PR, git should automatically link it to the regro-cf-autotick-bot remote if this is the only remote with a branch of that name. It is not possible to push to a GitHub repository using the This means if you push a version update to a branch and then create a PR, conda packages will be published to before the PR is merged. This means that a maintainer can create branches in the main repo.įor updates, using a branch in the main repo is discouraged because, Forking and pull requests ¶Īll maintainers are given push access to the feedstocks that they maintain. If you need to remove a package, please see the section on marking packages broken. Upload packages which already exist on the conda-forge channel. Note that because of this policy, our upload scripts will refuse to Policy is very important as it increases the reliability and reproducibility of conda environments ![]() Maintaining packages ¶ Important notes ¶ Packages on conda-forge are immutable ¶Īs a matter of policy, we do not allow edits or the deletion of packages on conda-forge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |