Non-push events? #9

Open
opened 2020-04-28 12:33:57 +00:00 by southerntofu · 0 comments
Owner

We could support passing the full webhook to triggers for further processing. STDIN is a good candidate for passing this. Would allow to script issues/PRs (for example for an IRC bot).

However, some tasks may only want to receive push updates (to build/test). Maybe requires to tweak git-build to let it manage non-push events?

Related: we could let git-build know a specific branch was updated in order not to trigger all tasks on branches that had no update? Actually git-build should not run the task if there was no update on the target branch. if it does it's a bug

We could support passing the full webhook to triggers for further processing. STDIN is a good candidate for passing this. Would allow to script issues/PRs (for example for an IRC bot). However, some tasks may only want to receive push updates (to build/test). Maybe requires to tweak git-build to let it manage non-push events? Related: we could let git-build know a specific branch was updated in order not to trigger all tasks on branches that had no update? Actually git-build should not run the task if there was no update on the target branch. if it does it's a bug
This repo is archived. You cannot comment on issues.
No Label
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: forge/archive_hook.sh#9
No description provided.