-
Notifications
You must be signed in to change notification settings - Fork 129
Possibility to name the branch NuKeeper makes for adding the updates #813
Comments
This is already possible with the |
I don't think that is the feature that @StephanTuinder wants. Say you have a working branch named |
@MaxMommersteeg Correct |
Besides from more control over branch naming, does this introduce any other functionality that isn't available right now with target branch option? |
targetbranch option selects the branch Nukeeper will run against. I propose a feature with which you can determine what the branch nukeeper creates and updates will be named. |
It would be great as we have branch name checks for Pull Requests. |
PR is waiting to be approved for this: #841 |
…(Feature #813) (#841) * All is there except for BitBucketLocal, working on that. * test fix * BitBucketLocal update. * Textual change and site update * Fix Conflicts * Fixes after merge and test * test fix after merge * typo * Removed coda that potentially could destroy work * Some fixes SonarQube pointed out and fixes for GitCmdDriver(test) * usings fix * added NukeeperLogger to last test Co-authored-by: Stephan Tuinder <stuinder@sib.inlichtingenbureau.nl>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
🚀 Feature Requests
possibility to name the branch NuKeeper makes for adding the updates
Contextualize the feature
By naming the branch NuKeeper creates, it is possible to make several runs of NuKeeper
contribute to the same pullrequest.
Also it makes it possible to have a coherent naming of branches that belong to each other:
Nuget code updated for "AwsomeFeature". For all NuKeeper updates of this nuget the branch/pullrequest can also be named "AwsomeFeature"
Describe the feature
If the branchname is given, NuKeeper should check if this branch exists and skip creating the branch, if not, it should create the branch with the given name.
If the pullrequest exists on given branch NuKeeper should skip creating the pullrequest.
Platforms affected (mark all that apply)
The text was updated successfully, but these errors were encountered: