Action required: Greenkeeper could not be activated 🚨
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Inspect the repository's CI configuration and verify that it reports a commit status for the greenkeeper/initial branch, or for branches prefixed with greenkeeper/. After CI is configured, use Greenkeeper's account.fix repo button to re-trigger the initial pull request and confirm that Greenkeeper activates.
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
- TypeScript
- Stars
- 141
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor 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.
More from callstack/component-docs
-
callstack/component-docs#49 · 1 comment · 2 reactions · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
callstack/component-docs#48 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
callstack/component-docs#44 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
callstack/component-docs#34 ·
-
Support RNW Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
callstack/component-docs#30 · 1 reaction ·
All issues in callstack/component-docs
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·