Actions: Consider splitting "playground" out of production "environment"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
At the moment GitHub Actions only have a notion of "production" environment, which includes both "production" and "playground". The "staging" environment is separate.
However, we only use "staging" for pull request and manual testing, and there's no real data there. OTOH, "playground" has quite a bit of data sent by various people, and it would be good to have the deployment confirmation cut off after it, and not after just "staging", so that we can catch more potential issues before deploying to actual production.
Consider separating "playground" into its own "environment" in terms of GitHub Actions.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Inspect the repository's GitHub Actions workflow configurations and identify how staging, playground, and production deployments are currently represented. Confirm the deployment order and approval points, then separate playground as its own environment so confirmation occurs after playground and before production. Done means the workflow reflects the requested environment boundaries and remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100