Buildbot: Approving workflows approach to the PRs #93
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#93
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently the only way to trigger CI from a PR is to manually poke
blender-bot
, which not all of developers remember to do before landing PR.Ideally all PRs will eventually run CI/CD automatically, but there are some other things to happen first (#44).
Meanwhile, it might be good idea to use "Approve workflow" functionality (if it exists in Gitea).
The main motivation of investigating this approach is to have something showing up in the face of maintainers, with an easy way of triggering automated tests.