mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2026-03-22 12:44:37 -05:00
Action required: Greenkeeper could not be activated 🚨 #60
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/conventionalcommits.org#60
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @greenkeeper[bot] on GitHub (Feb 18, 2019).
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the
greenkeeper/initialbranch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with
greenkeeper/.Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
@damianopetrungaro commented on GitHub (Feb 18, 2019):
I don't think we are using greenkeeper.
Going to remove the access if it is there.
@damianopetrungaro commented on GitHub (Feb 18, 2019):
@hutson do you know sth about this?
@hutson commented on GitHub (Feb 19, 2019):
I know what Greenkeeper is, but I don't know how it became activated on this repository. 🤷♂️
Maybe @bcoe might know (He has been working overtime updating/upgrading many of our organization repositories to use the latest dependency releases)
@bcoe commented on GitHub (Feb 19, 2019):
@damianopetrungaro @hutson Greenkeeper was an attempt to address https://github.com/conventional-commits/conventionalcommits.org/issues/127, it keeps package.json up-to-date.
I don't have a strong opinion as to whether we need to do this or not. If we want to address #127, I suggest installing GreenKeeper, if not let's close #127 and just keep updating things manually.
@bcoe commented on GitHub (Feb 19, 2019):
seems like getting some smoke tests running in CI wouldn't be the worst idea in the world ... regardless of whether we enable GreenKeeper.
@damianopetrungaro commented on GitHub (Feb 19, 2019):
Cool! I thought it was a spam message or enabled by mistake, totally fine with it @bcoe :D
@hutson commented on GitHub (Feb 20, 2019):
I would love to see dependency updates automated with Greenkeeper!
@damianopetrungaro commented on GitHub (Jul 4, 2019):
@bcoe any update on this? Or can we close it? (see https://github.com/conventional-commits/conventionalcommits.org/issues/127#issuecomment-508423779)
@bcoe commented on GitHub (Jul 8, 2019):
@damianopetrungaro let's close this for now, if someone else wants to revisit and configure appropriately we can.