-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Add project workflow feature so users can define how to execute steps when project related events fired #30205
base: main
Are you sure you want to change the base?
Conversation
… when project related events fired
I'm now hesitate to add this feature because looks like some actions can do the same things. Like https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions and more third-party actions can do it easier. |
I would really like to see this merged, I am waiting for the ability to automatically set a project for a new issue via the issue template (#25028). GitHub provides this through an "org-name/BOARD_ID" syntax as announced here. I think having to set up an action for that (which would also require to set up a runner?) is quite cumbersome for such a simple feature. |
I do not know, but firing up multiple containers to just set a specific label or remove a label, or even re-open or close an issue as part of the workflow seems to be overkill to me, what do you think? |
What's the status here now? This is quite a wanted feature. |
Yes, this is a good reason to use the internal implementation rather than CI/CD. I will continue this work. |
Great, thx for your feedback. I am really looking forward to it. |
As far as I understand the description, this will depend on Workflows? |
No. This is project workflow which is different from Actions workflow. |
And what's better? Storing the workflows in the special YAML files on the default branch or storing them in the database? This is a block to prevent me from continuing the work. |
I would purpose to store them in the database. Branches are for code changes and depending stuff but this is a projekt management feature that is specific for gitea. i.e.: If you mirror your code to an other git system like github the projekt workflows are only garbage there. |
but storing in the db will require some form of UI to create/edit. |
For my defence I didn't know about the templates and the storage path. In that case I would agree to that argument. |
This PR supports repository workflow files under
.gitea/projects/
to response to projects related events and do some actions. For org project, maybe we can readorgname/.profile
repository.Resolve #13498
Resolve #14359
Resolve #26704
Resolve #27990
Resolve #25028
Replace #28745