typelevel / typelevel/sbt-typelevel
Customize `on:` triggers (separate `push` and `pull_request` triggers)
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 185
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
I want to define this trigger in my workflow:
on:
push:
branches:
- main
pull_request:
types: [synchronize, opened, reopened]
Or even:
on:
pull_request:
merge_group:
Which will run a build on my main branch, and for any pull request activity. Currently a lot of PR's will have the same job running twice (for push and pull_request activity). Is there a way to define this in the GHA plugin?
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 by tracing the GHA plugin configuration that generates the workflow on: block. Compare the requested separate push, pull_request, and merge_group trigger forms, then determine how existing workflow generation tests cover trigger behavior. Done means users can configure these triggers independently without duplicate builds for pull request activity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, scala
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100