Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gitea Actions Workflow dispatch rest api #33525

Closed

Conversation

ChristopherHX
Copy link
Contributor

adds new repo rest api based on https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#create-a-workflow-dispatch-event

  • /workflows/{workflow_id}/dispatches
  • moves dispatch logic into actions_service package
  • adds tests for the rest api
  • a PAT with repo:write might be required

Closes #32041

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Feb 6, 2025
@pull-request-size pull-request-size bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Feb 6, 2025
@github-actions github-actions bot added modifies/api This PR adds API routes or modifies them modifies/go Pull requests that update Go code labels Feb 6, 2025
@lunny
Copy link
Member

lunny commented Feb 6, 2025

Looks like a duplication of #32059

@ChristopherHX
Copy link
Contributor Author

Oh, the tests could be copied to the other much bigger change that lacks them.

I will test the existing PR now

Gitea is a big project :), thanks for letting me know

@ChristopherHX
Copy link
Contributor Author

Closing changes fully migrated to the change #32059

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. modifies/api This PR adds API routes or modifies them modifies/go Pull requests that update Go code size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Trigger workflow B in a repo from workflow A in another repo
3 participants