Action required: Greenkeeper could not be activated 🚨
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
Research direction
No repository file or test is named. Check whether CI reports a commit status on the greenkeeper/initial branch, then review the repository's CI configuration and the Greenkeeper account's “fix repo” action. Done means CI reports statuses on the required branches and Greenkeeper can be re-triggered successfully.
Written by the indexing model from the issue text.
Description
🚨 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/initial branch, 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.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Riloox/hostkind-open#45 ·
-
Request: semgrepOpennew icon permissions in review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
simple-icons/simple-icons#15093 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
module-federation/core#5205 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
aikido security:critical
Difficulty 1/5 Under an hour Newbie friendliness 76/100
dequelabs/monitor-utility#63 ·