github/government.github.com

"Ensure entries are GitHub Orgs" takes a long time to run, surfaces problems unrelated to changes in a given PR

Open

#1,265 opened on Dec 22, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (1,613 stars) (1,040 forks)batch import
help wanted

Description

  • run "Ensure entries are GitHub Orgs" on all entries periodically (weekly?), generate issue or pr if failures occur
  • only check changed/added entries in given PR

Contributor guide

Tech stack
None
Domain
ci cddeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic scripting knowledgeGitHub Actions YAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the existing CI workflow files in the repository, likely in .github/workflows, to find the script that implements the 'Ensure entries are GitHub Orgs' check. Look at the script's code to understand how it currently runs only on changed entries in a PR. The issue suggests two changes: (1) add a periodic run (e.g., weekly via cron) to check all entries, and (2) modify the PR trigger to only check changed/added entries instead of all entries. Review maintainer comments in the issue for any additional constraints.