Skip to content

fix(gitlab): add support for gitlab subgroups #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 31, 2017
Merged

fix(gitlab): add support for gitlab subgroups #8

merged 1 commit into from
Aug 31, 2017

Conversation

canercandan
Copy link
Contributor

#7

@canercandan canercandan mentioned this pull request Jun 12, 2017
Closed
@hutson
Copy link

hutson commented Jun 12, 2017

👍 Looks good to me.

@canercandan canercandan force-pushed the repo-utils/parse-github-repo-url#7 branch 2 times, most recently from 1b30822 to e3e0a9c Compare June 13, 2017 16:27
@canercandan canercandan force-pushed the repo-utils/parse-github-repo-url#7 branch from e3e0a9c to d40123d Compare June 14, 2017 09:48
@hutson
Copy link

hutson commented Jun 15, 2017

👍 Following on the most recent changes, I'm reaffirming that this change looks good.

@bahmutov bahmutov merged commit 1fa80ee into repo-utils:master Aug 31, 2017
@bahmutov
Copy link
Collaborator

First time TravisCI could not publish the new version

1.97s$ npm run semantic-release
> [email protected] semantic-release /home/travis/build/repo-utils/parse-github-repo-url
> semantic-release pre && npm publish && semantic-release post
npm ERR! publish Failed PUT 401
npm ERR! Linux 4.8.12-040812-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.8.4/bin/node" "/home/travis/.nvm/versions/node/v4.8.4/bin/npm" "publish"
npm ERR! node v4.8.4
npm ERR! npm  v2.15.12
npm ERR! code E401
npm ERR! You must be logged in to publish packages. : parse-github-repo-url

Seems the NPM_TOKEN has been disabled. I refreshed this and GH_TOKEN using semantic-release-cli, hope it solves the issue.

@bahmutov
Copy link
Collaborator

Yes, it did - published https://github.com/repo-utils/parse-github-repo-url/releases/tag/v1.4.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@canercandan @hutson @bahmutov