Action required: Greenkeeper could not be activated 🚨
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start by checking the greenkeeper/initial branch and whether this repository reports CI commit statuses on all branches. Review the CI configuration and confirm that greenkeeper/* branches are included. After CI is correctly configured, use the Greenkeeper account's “fix repo” action to re-trigger the initial pull request and verify that a status is reported.
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
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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.
More from donejs/bit-docs-donejs-theme
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
donejs/bit-docs-donejs-theme#71 · 5 comments ·
-
bug developer relations easy help wanted
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
bug developer relations help wanted p2
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
bug developer relations help wanted p2
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
bug developer relations help wanted p2
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in donejs/bit-docs-donejs-theme
Similar issues
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
zmo2s/agent-toolbox#22 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
agent: ready area: infrastructure area: submission priority: high type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dkritarth/scopewatch#204 ·
Maintainers usually reply within 1 day
-
enhancement good first issue Stellar Wave trivial
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
StellarCanary/ProtocolCanary-Action#331 ·
Maintainers usually reply within 1 day
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Hochfrequenz/aibap.mcp#578 ·
Maintainers usually reply within 1 day