Repository navigation
#8 2/2 - Add getLabels-func + copy labels functionality from one repo to others - #23
Merged
rajikaimal merged 1 commit intoOct 24, 2016
Conversation
Contributor
|
Awesome work @codingCookie |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added a new function + a flow where I ask the user if he wants to copy labels from one repo to others.
It's the second bulletpoint from issue #8
It may come to merge conflicts when PR #22 will make his way in the master (both branches are from master and both branches have console.logs added to 'createLabel()'
++ function getLabels
++ first flow by asking the user if he want to copy labels from an existing repo to others
connects to #8