liquidmetal-dev / liquidmetal-dev/flintlock
Redirect CI Slack notifications to the the community channel
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
* [community channel](https://weave-community.slack.com/archives/C02KARWGR7S)
* Relevant files:
* https://github.com/weaveworks-liquidmetal/flintlock/blob/main/.github/workflows/fork.yaml#L71
* https://github.com/weaveworks-liquidmetal/flintlock/blob/main/.github/workflows/nightly_e2e.yml#L42
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
Start with .github/workflows/fork.yaml at line 71 and .github/workflows/nightly_e2e.yml at line 42. Review how each workflow sends CI notifications, update both destinations to the linked community channel, and run the relevant workflows or inspect their notification configuration to confirm they target that channel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100