Limits CodeQL workflow to run only in the Apache Airflow repo#11264
Merged
potiuk merged 1 commit intoapache:masterfrom Oct 4, 2020
Merged
Conversation
It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days.
turbaszek
approved these changes
Oct 4, 2020
potiuk
added a commit
that referenced
this pull request
Oct 6, 2020
It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days. (cherry picked from commit 1b9e59c)
RaviTezu
pushed a commit
to RaviTezu/airflow
that referenced
this pull request
Oct 25, 2020
…#11264) It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days. (cherry picked from commit 1b9e59c)
kaxil
pushed a commit
that referenced
this pull request
Nov 12, 2020
It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days. (cherry picked from commit 1b9e59c)
potiuk
added
the
type:misc/internal
potiuk
added a commit
that referenced
this pull request
Nov 16, 2020
It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days. (cherry picked from commit 1b9e59c)
kaxil
pushed a commit
that referenced
this pull request
Nov 18, 2020
It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days. (cherry picked from commit 1b9e59c)
cfei18
pushed a commit
to cfei18/incubator-airflow
that referenced
this pull request
Mar 5, 2021
…#11264) It has been raised quite a few times that workflow added in forked repositories might be pretty invasive for the forks - especially when it comes to scheduled workflows as they might eat quota or at least jobs for those organisations/people who fork repositories. This is not strictly necessary because Recently GitHub recognized this as being a problem and introduced new rules for scheduled workflows. But for people who are already forked, it would be nice to not run those actions. It is enough that the CodeQL check is done when PR is opened to the "apache/airflow" repository. Quote from the emails received by Github (no public URL explaining it yet): > Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. We’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: > * Starting today, scheduled workflows will be disabled by default in new forks of public repositories. > * Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days. (cherry picked from commit 1b9e59c)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It has been raised quite a few times that workflow added in forked
repositories might be pretty invasive for the forks - especially
when it comes to scheduled workflows as they might eat quota
or at least jobs for those organisations/people who fork
repositories.
This is not strictly necessary because Recently GitHub recognized this as being
a problem and introduced new rules for scheduled workflows. But for people who
are already forked, it would be nice to not run those actions. It is enough
that the CodeQL check is done when PR is opened to the "apache/airflow"
repository.
Quote from the emails received by Github (no public URL explaining it yet):
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.