Yes - it is scheduled to run on a cron job (I hadn't realized that it was triggered by cron job too)
If you can't ignore the failing runs, you turn off GitHub actions on your fork of eclipse.platform, here is a screenshot on my fork:
I was studiously trying to ignore the error. But I can't anymore. I don't understand what's going wrong. If I'm to report this as a bug for the aggregator, I'm not sure what
I'd say except to point to the failing codeQL. I'd like to understand if I caused this, or if it is a bug.
You did not cause this, nor is it really a bug. The GitHub actions workflows are designed to be run on eclipse-platform (as opposed to your fork). Perhaps it is possible to improve the workflows so that they handle running on forks better.
So you're saying there was a push attempt to master on eclipse-platform/eclipse.platform, rather than chgenly/eclipse.platform? What are you looking at that tells you this?
>> When you create the Pull Request back to Eclipse the workflows should run as expected
I'm not sure what you mean by this. There is an existing pull request:
The workflows are running as expected there:
Note that I had to press Enable and run on the workflows on the PR as you are a first time contributor. Once you get your first PR approved, future PRs will automatically run the workflows.
I hope that helps,
From: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
Sent: Friday, August 25, 2023 12:05 PM
To: Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>
Cc: Christopher Genly <genly@xxxxxxxxxxxxxxxxx>
Subject: Re: [platform-dev] What does this mean: The nested job 'message-check' is requesting 'pull-requests: read', but is only allowed 'pull-requests: none'?
When you create the Pull Request back to Eclipse the workflows should run as expected.
I just pushed a change to my branch. This error is reported:
workflow file: .github/workflows/ci.yml#L16
The workflow is not valid. .github/workflows/ci.yml (Line: 16, Col: 3): Error calling workflow 'eclipse-platform/eclipse.platform.releng.aggregator/.github/workflows/checkMergeCommits.yml@master'. The nested job 'message-check' is requesting 'pull-requests:
read', but is only allowed 'pull-requests: none'.
This is from:
What does it mean and how do I fix it?
This is where my fork is:
platform-dev mailing list
To unsubscribe from this list, visit