CrowdStrike / CrowdStrike/falcon-operator
[feature request] Ensure releases are on github before sending out customer tech updates
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 79
- Forks
- 51
- Avg merge
- 6h 46m
- Merged PRs (30d)
- 10
Description
For instance the email announcing 1.3.1 has gone out but the 1.3.1 release is not yet available on github.
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.
Research direction
No files, tests, or entry points are named. Start by tracing how the 1.3.1 release is published on GitHub and how customer tech updates are sent; define the sequencing requirement and verify that an update cannot go out before the corresponding release is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100