Skip to content

Add contribution guidelines and recommendations documents - #18

Merged
yorkerhodes3 merged 3 commits into
mainfrom
agents/refresh-from-github-repo
Aug 8, 2026
Merged

Add contribution guidelines and recommendations documents#18
yorkerhodes3 merged 3 commits into
mainfrom
agents/refresh-from-github-repo

Conversation

@yorkerhodes3

Copy link
Copy Markdown
Contributor

This pull request introduces several key documents to enhance the contribution process and site management for the Ethical Tech CoLab website:

  • HOW-TO-CONTRIBUTE.md: Provides a comprehensive guide on safe branching, source validation, generated-site management, PR submission, and deployment workflows.
  • SITE-CONTROL-RECOMMENDATIONS.md: Outlines best practices for branch protection, ownership, continuous integration, and governance of AI workflows.
  • UPDATES-NEEDED.md: Lists 11 verified legacy issues and includes nine review-only requests for Carolina, focusing on tools, skills, and processes for effective contributions.

Additionally, the README.md has been updated to include links to these new documents, ensuring that contributors can easily access the necessary guidelines. No backlog entries or GitHub issues were created as part of this update.

Yorke Rhodes III and others added 2 commits August 8, 2026 13:01
Rename HOW-TO-CONTRIBUTE.md to CONTRIBUTING.md so GitHub surfaces it on the
new-issue and new-PR forms; it is currently the only gate on contribution
quality, since there is no branch protection, PR CI, or PR template yet.

Replace first-name maintainer references with the public GitHub handles
(@carolina-moron, @alx-du) and point contributors at review roles rather than
one person. Rekey the section B drafts from CAR-nn to WF-nn so they read as
questions about the maintenance workflow rather than about an individual.

Record the blocker on UPD-002: the gh token has no workflow scope, so any push
touching .github/workflows/* is rejected (BACKLOG.md section 8). That gates the
pull-request CI item and the required-build control that depends on it, so it
now leads the recommended implementation order.

Correct the README site map: cohort history moved to the Home route via
CohortsShowcase, the 404 note now clearly belongs to /about, and src/lib/ is
listed because CONTRIBUTING.md requires asset() for public/ paths.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
UPD-005 described the snapshot as touching hundreds of files during normal
regeneration without saying why, which led to it being read as staleness. The
cause was the random Next.js build ID embedded in every prerendered document,
and it is now pinned in the snapshot copy, so the item's premise and its
acceptance criteria needed correcting.

Also records the blocker that would otherwise defeat the proposed drift check:
the repository has no .gitattributes while Git for Windows defaults to
core.autocrlf=true, so a Windows checkout reports hundreds of modified snapshot
files that have no content change.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant