You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Github's technique for PRs is to fork the repo, create a new branch with the new feature and then submit a PR to the original repo. If it is desired to test build the new feature using dr then, currently, the branch must be manually cloned into the original repo and then built. This branch is then redundant and will probably be deleted from the base repo (it will probably also become outdated fairly quickly as well).
This process should be made easier. Maybe something like dr build-fork <repo> <branch>.
dr could potentially do a git remote add <repo>, checkout the branch and then build from there. Would probably need to clean up too ;-)
The text was updated successfully, but these errors were encountered:
Sorry, @Ealdwulf pointed out that I didn't mention that this is for users external to the organisation who is running the kano-repository-manager software.
Github's technique for PRs is to fork the repo, create a new branch with the new feature and then submit a PR to the original repo. If it is desired to test build the new feature using dr then, currently, the branch must be manually cloned into the original repo and then built. This branch is then redundant and will probably be deleted from the base repo (it will probably also become outdated fairly quickly as well).
This process should be made easier. Maybe something like
dr build-fork <repo> <branch>
.dr
could potentially do agit remote add <repo>
, checkout the branch and then build from there. Would probably need to clean up too ;-)The text was updated successfully, but these errors were encountered: