Brad Rydzewski

In terms of a temporary workaround, I think we could do something here: https://github.com/drone/drone/blob/master/remote/github/convert.go#L218 ```diff func convertDeployHook(from *webhook) *model.Build { build := &model.Build{ Event: model.EventDeploy, Commit: from.Deployment.Sha, Link: from.Deployment.URL, Message:...

I want to amend my previous suggested solution. As of 1.0 we can fetch the commit details from the remote repository. We can therefore use the sha to get the...

Instead of removing errgroup, I feel like we could fix with a small change to use `errgroup.WithContext`. When the derived context is cancelled it should cancel all remaining subroutines, since...

```text trigger: event: include: - pull_request action: include: - closed ``` > Which worked with > - Creating the PR > - Updating the PR > - Closing the PR...

thanks for providing the examples. the logic needs to be slightly adjusted to avoid breaking the current excludes behavior. Basically if the action is closed, the pipeline should only execute...

the below example should not create a pipeline for a pipeline closed event. There may be teams already using the below syntax (for synchronization actions) and they will not expect...

real estate on this particular screen is a bit limited, but if you click the visual view you can find the runner name.

I think there two interesting use cases here, from what I can tell: 1. the ability to support mono repos, where a single repository consists of multiple loosely coupled projects....

So do we need the ability to limit steps by files or folders changed? Or load different yamls based on files or folders changes? Or both? > A mono repo...

Perhaps instead of sub-yaml we define sub-projects in Drone? It is conceptually similar, but perhaps more general purpose and might support more use cases. For example: 1. drone/drone has the...