Avoid run tests on branch `gh-pages` in Heroku
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
The issue concerns the gh-pages branch, MkDocs deployment via mkdocs gh-deploy --force, and Heroku CI. Start by inspecting the GitHub Actions workflow and CI configuration; done means updates to gh-pages no longer trigger the test run that currently fails.
Written by the indexing model from the issue text.
Description
The gh-pages is managed by MkDocs, I not want every time MkDocs is deployed with Github Actions with the command mkdocs gh-deploy --force, because that branch never ever would contains tests, that cause the CI in Heroku fail each time this branch is updated, but that is a bad approach and ends by waste the resources and money of Heroku and me
- Dominant language
- TypeScript
- Stars
- 888
- Forks
- 236
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 36
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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.
More from heroku/cli
-
The APT installer for the CLI should create a file in deb822 format on Ubuntu 26.04Possibly taken @ChipV223 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
heroku/cli#3974 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
heroku/cli#3867 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
config:get does not distinguish between unset and empty env varsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 62/100
heroku/cli#3450 · 4 comments ·
Maintainers usually reply within 1 day
-
on-call reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
on-call reviewed
Difficulty 4/5 3-5 days Newbie friendliness 35/100
heroku/cli#3222 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
area: desktop area: website priority: P2 type: feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
appandflow/stim#3411 · 1 comment ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rjsf-team/react-jsonschema-form#5485 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 65/100
lingdojo/kana-dojo#32090 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Friction: Org home and org switcher copy still say repositories and connected agents live in the personal accountPossibly taken A pull request linked to this issue is open or already merged. Openfriction
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
kentcdodds/kody#3265 ·
Maintainers usually reply within 1 day