-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Description
Help us understand the severity of this issue
- breakage; unable to contribute or trigger builds will no workarounds
- inconvenient workarounds exist, but significant effort required
- needed for a Flutter team-wide priority (already agreed upon)
- nice-to-have; none of the above
What do you need help with
I would like to be able to use peter-evans/create-pull-request@v7, peter-evans/repository-dispatch@v4, GuillaumeFalourd/branch-exists@v1.1 in flutter/package workflow
For peter-evans/repository-dispatch@v4
As part of setting up batch release, I would like to leverage repository dispatch action so that we can reuse workflow for different configuration.
The current use case is that I have a general workflow to create a PR for batch release https://github.com/flutter/packages/blob/main/.github/workflows/batch_release_pr.yml
and then each package who wants to opts in can create a dispatching workflow that looks similar to
https://github.com/flutter/packages/blob/main/.github/workflows/go_router_batch.yml
where they can specify targeted package, cron schedule.. etc
For peter-evans/create-pull-request@v7
Create pull request as title the action suggest. The workaround will be do this in the plugin tool using github package, but using ready available GA makes things easier.
For GuillaumeFalourd/branch-exists@v1.1
This is used in https://github.com/flutter/packages/blob/main/.github/workflows/batch_release_pr.yml to make sure the branch is successfully created before moving on to create PR. Again, we can write a new command to do that in plugin tool, but then we will have to maintain the code.
The error message shows this actions are now allowed.
https://github.com/flutter/packages/actions/runs/19627518158
Metadata
Metadata
Assignees
Labels
Type
Projects
Status