Skip to content
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.

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

Make CI green again #150

Merged
merged 3 commits into from
Aug 14, 2018
Merged

Conversation

pablobirukov
Copy link
Contributor

No description provided.

member_check: true
}
member_check: true,
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just a JSON literal does not need a semicolon. All you semicolon lovers 😅

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, normally your IDE should pick up eslint config and blame you for not following the standard.

Anyway, who cares, let's just make CI happy and green

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well my vscode did not pickup any eslint errors, did not have the extension installed 😢

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe setup pre-commit hook to run "lint" script?

}

return RequestHelper.put(this, `projects/${pId}/push_rule`, args);
return RequestHelper.put(this, `projects/${pId}/push_rule`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be options as second argument since it is a put.

@pablobirukov
Copy link
Contributor Author

@Casz can you please take a look at the failing PushRule test?

If you don't have time at the moment, I'd suggest to disable the test and proceed w/ merge, so that CI can start revealing problems in pending pulls

@pablobirukov
Copy link
Contributor Author

pablobirukov commented Aug 14, 2018

Oh, wait a second. Did it ever work? It should not work w/o license uploaded since it's an EE feature

https://gitlab.com/gitlab-org/gitlab-ee/issues/3825

@jetersen
Copy link
Contributor

Ehh sorry did not think of that @R00GER my bad 😭

@pablobirukov
Copy link
Contributor Author

@jdalrymple 🎉

@jetersen
Copy link
Contributor

caching can be evil 😈

@jdalrymple
Copy link
Owner

Omg 👏🏽👏🏽👏🏽👏🏽🎉🎉🎉🎉🎉🎉

@jdalrymple jdalrymple merged commit 09c2ab4 into jdalrymple:master Aug 14, 2018
@jdalrymple
Copy link
Owner

🎉 This PR is included in version 3.8.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

mdsb100 pushed a commit to mdsb100/node-gitlab that referenced this pull request Aug 17, 2018
* Disable cache on travis

* Fix linter failures

* Disable PushRule test (EE-only feature)
mdsb100 pushed a commit to mdsb100/node-gitlab that referenced this pull request Aug 17, 2018
* Disable cache on travis

* Fix linter failures

* Disable PushRule test (EE-only feature)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants