Not for code contributions - the source code is remote.
Orchestrate ETL and data processing pipeline for Hacktoberfest GitHub PR statistical analysis:
- Regularly between
YYYY-09-30-10:00:00andYYYY-11-01-14:00:00UTC for- valid PRs merged to repos
- accepted valid PRs not merged to repos
- Valid PRs are
- to repositories with the
hacktoberfesttopic or have thehacktoberfest-acceptedlabel, and - created between
YYYY-09-30-10:00:00andYYYY-11-01-14:00:00UTC, and - not be labelled either
spamorinvalidif not labelledhacktoberfest-accepted, and - not a draft PR
- to repositories with the
- Accepted PRs must be valid and, between
YYYY-09-30-10:00:00andYYYY-11-01-14:00:00UTC, either- merged, or
- open and labelled with
hacktoberfest-accepted
- Excludes PR review acceptance criteria on assumption of being merged if all code owners approve
- Does not account for PR disqualification aside for PR labels
spamandinvalid - Assumes included repositories meet other requirements to be valid for hacktoberfest
- includes fork repos, owned by PR creators or not, assuming they meet acceptance criteria
- accepted PR data for repos removed following API-fetching day(s) will be included in the stats
- For
iin{1,...,4}, create a repository Action namedGH_TOKEN_<i>using a unique personal access token with:Public repositories- note:
imust match the job matrix in.github/workflows/sync_parallel_step.yml
- Create a repository Action named
REPO_NAMEusing the<owner/repository>name the source code is hosted in. - Create a repository Action named
REPO_TOKENusing a personal access token with:- the
Resource ownermatching theownerin the<owner/repository>name set to theREPO_NAMEaction Only select repositories:- the repository matching the
<owner/repository>name set toREPO_NAME
- the repository matching the
Add permissions:Contents:Read and write
- the
- Create a repository Action named
KEYusing a base64-encoded random key 🔑:base64.urlsafe_b64encode(key=os.urandom(32)).decode()