Thanks for your tips. Honestly I’m not so deep with git and could not real follow what you try to explain me. This will be also another reason why I started to work directly on the cordova resositories.
Von: Norman Breau via dev <[email protected]> Datum: Donnerstag, 27. August 2026 um 13:50 An: [email protected] <[email protected]> Cc: Norman Breau <[email protected]> Betreff: Re: AW: [DISCUSS] GitHub Actions Workflow Push Event A single git checkout can contain multiple upstreams. What I do is all my forked repos `origin` upstream is my own fork. `git remote add apache <apacheURL>` for the apache remote. `git fetch apache` to pull down apache remote, at which point you're free to `git checkout apache/main` or anything that is directly on the apache repo. I'm not stating this as support for one method over another, I'm just stating that you can have both the apache repo and the fork repo as part of the same checkout, which coincidentally allows you to easily sync your fork with the apache upstream as well, without going to the Github UI. As for the push event suggestion, I don't foresee any problems with it. On 2026-08-27 8:15 a.m., Manuel Beck wrote: > Regarding: > if we should recommend using forked repos for development work only instead. > When I started to develop for Cordova I found it more easier to create PR > branches upstream, rather than on a fork. Because than I only have on > repository to check out, not two. When testing something, sometimes I need > the real repo, sometimes the fork. To make work easier I started to only use > the upstream repository. > > Von: Bryan Ellis <[email protected]> > Datum: Donnerstag, 27. August 2026 um 13:03 > An: [email protected] <[email protected]> > Betreff: [DISCUSS] GitHub Actions Workflow Push Event > > I would like to update how the push event for our GitHub Actions workflow > is configured. > > Currently, we have the following: > > ``` > on: > push: > branches-ignore: > - 'dependabot/**' > ``` > > This prevents the workflow from executing when commits are pushed to > branches prefixed with dependabot, which is correct, but does not exclude > other development branches. > I was looking into this configuration because PRs show duplicate checks > (one for push and one for PR). This is noticeable for those who create > branches upstream, instead of creating on a forked repo. > > I was wondering if we could modify to the following: > > ``` > on: > push: > branches: > - 'master' > - '[0-9]+-[0-9]+-x' > ``` > > Instead of configuring which branches to ignore, we would define which > branches should run. > > I was wondering if this could be avoided somehow, if it is related to this > push event, the overall desired behavior, and if we should recommend using > forked repos for development work only instead. > > Does anyone have any concerns or reasons if this change is undesirable > compared with the current configuration? Or have any opinion about the > desired behavior or development workflow? > > If I understand the documentation correctly, I believe this configuration > should work and only run when commits are pushed to the master branch or > matching a release branch. > > I would need to test and confirm the behavior before making any changes, > but I have seen similar configurations in other projects and wanted to > raise this. > > References: > > - > https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onpushbranchestagsbranches-ignoretags-ignore > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
