how to deploy this from a PR branch
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- documentation
Research direction
Start with the README passage stating that configuration must be on the default branch. Check the documented deployment behavior for configuration kept on a pull request branch, then update the relevant documentation to explain whether an administrator must add it to the default branch and what users should expect before it is merged.
Written by the indexing model from the issue text.
Description
The readme says that "The configuration must be on the default branch" for this to work. It'd be good if the docs could cover how one is supposed to deploy this to a repo where changes have to go the default branch via PR. Is that possible? or should the admin with access to the default branch add the config? what happens while the config is still on a PR branch?
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 438
- Avg merge
- 27d 8h
- Merged PRs (30d)
- 1
Getting set up
- No 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 actions/stale
-
Stale label remains after pushing a new commitPossibly taken @v-chiranjib-swain claimed this 21 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Closing items while paginating can skip open pull requestsPossibly taken @v-chiranjib-swain claimed this 93 days ago. Openbug
-
Ignore issues which has linked open PRsPossibly taken A pull request linked to this issue is open or already merged. Openfeature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
🛠️ dette technique
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
betagouv/mon-entreprise#4752 · 1 comment ·
Maintainers usually reply within 5 days
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Maintainers usually reply within 2 days
-
area/providers type/feature version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#64845 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day