From 1299027f655f6d21f21db61029ad779523c84839 Mon Sep 17 00:00:00 2001 From: Natalia Luzuriaga Date: Tue, 13 Oct 2026 10:23:28 -0700 Subject: [PATCH 1/8] Add new COMMUNITY.md file and remove old doc files Signed-off-by: Natalia Luzuriaga --- COMMUNITY.md | 108 +++++++++++++++ COMMUNITY_GUIDELINES.md | 37 ----- MAINTAINERS.md | 292 ---------------------------------------- 3 files changed, 108 insertions(+), 329 deletions(-) create mode 100644 COMMUNITY.md delete mode 100644 COMMUNITY_GUIDELINES.md delete mode 100644 MAINTAINERS.md diff --git a/COMMUNITY.md b/COMMUNITY.md new file mode 100644 index 0000000..02062ac --- /dev/null +++ b/COMMUNITY.md @@ -0,0 +1,108 @@ +# COMMUNITY.md + +codejson-generator is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals. + +## Project Members + +| Role | Name | Affiliation | +| :---------------- | :---------------- | :---------- | +| Open Source Lead | Remy DeCausemaker | CMS OSPO | +| Software Engineer | Natalia Luzuriaga | CMS OSPO | +| Software Engineer | Dinne Kopelevich | CMS OSPO | +| Software Engineer | Sachin Panayil | CMS OSPO | + +See [CODEOWNERS.md](.github/CODEOWNERS.md) for a list of those responsible for the code and documentation in this repository. + +See [Community Guidelines](#codejson-generator-open-source-community-guidelines) on principles and guidelines for participating in this open source project. + +## Roles & Responsibilities + +The members of codejson-generator community are responsible for guiding its development, ensuring quality standards, and fostering a collaborative environment. They play a vital role in making decisions about code contributions, handling releases, and ensuring the project meets its goals and objectives. Below is a list of the key members and their specific roles and responsibilities. We are eagerly seeking individuals who are interested in joining the community and helping shape and support these roles. + +### Maintainers: + +- [@natalialuzuriaga](https://github.com/natalialuzuriaga) +- [@decause-gov](https://github.com/decause-gov) +- [@sachin-panayil](https://github.com/sachin-panayil) +- [@DinneK](https://github.com/DinneK) + + + +### Approvers: + +- [@natalialuzuriaga](https://github.com/natalialuzuriaga) +- [@decause-gov](https://github.com/decause-gov) + + + +### Reviewers: + +- [@sachin-panayil](https://github.com/sachin-panayil) +- [@DinneK](https://github.com/DinneK) + + + +| Roles | Responsibilities | Requirements | Defined by | +| ---------- | :--------------------------------------------- | :-------------------------------------------------------------------------------- | :-------------------------------------------------------- | +| member | active contributor in the community | multiple contributions to the project. | PROJECT GitHub org Committer Team | +| reviewer | review contributions from other members | history of review and authorship in a sub-project | COMMUNITY file reviewer entry, and GitHub Org Triage Team | +| approver | approve accepting contributions | highly experienced and active reviewer + contributor to a sub-project | COMMUNITY file approver entry and GitHub Triage Team | +| maintainer | set direction and priorities for a sub-project | demonstrated responsibility and excellent technical judgement for the sub-project | COMMUNITY file owner entry and GitHub Org Admin Team | + + + +## Contributors + + + +![]() + + + + +### Alumni + +We'd like to acknowledge the following individuals for their past contributions of this project: + +- [@IsaacMilarky](https://github.com/IsaacMilarky) + +## codejson-generator Open Source Community Guidelines + +This document contains principles and guidelines for participating in the {{ cookiecutter.project_name }} open source community. + +### Principles + +These principles guide our data, product, and process decisions, architecture, and approach. + +- Open means transparent and participatory. +- We take a modular and modern approach to software development. +- We build open-source software and open-source process. +- We value ease of implementation. +- Fostering community includes building capacity and making our software and processes accessible to participants with diverse backgrounds and skillsets. +- Data (and data science) is as important as software and process. We build open data sets where possible. +- We strive for transparency for algorithms and places we might be introducing bias. + +### Community Guidelines + +All community members are expected to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). + +Information on contributing to this repository is available in our [Contributing file](CONTRIBUTING.md). + +When participating in codejson-generator open source community conversations and spaces, we ask individuals to follow the following guidelines: + +- When joining a conversation for the first time, please introduce yourself by providing a brief intro that includes: + - your related organization (if applicable) + - your pronouns + - your superpower, and how you hope to use it for codejson-generator +- Embrace a culture of learning, and educate each other. We are all entering this conversation from different starting points and with different backgrounds. There are no dumb questions. +- Take space and give space. We strive to create an equitable environment in which all are welcome and able to participate. We hope individuals feel comfortable voicing their opinions and providing contributions and will do our best to recognize and make space for individuals who may be struggling to find space here. Likewise, we expect individuals to recognize when they are taking up significant space and take a step back to allow room for others. + +- Be respectful. +- Default to positive. Assume others' contributions are legitimate and valuable and that they are made with good intention. + +### Acknowledgements + +The Community Guidelines sections were originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions. diff --git a/COMMUNITY_GUIDELINES.md b/COMMUNITY_GUIDELINES.md deleted file mode 100644 index 790a78d..0000000 --- a/COMMUNITY_GUIDELINES.md +++ /dev/null @@ -1,37 +0,0 @@ -# gov-codejson Open Source Community Guidelines - -This document contains principles and guidelines for participating in the gov-codejson open source community. - -## Principles - -These principles guide our data, product, and process decisions, architecture, and approach. - -- Open means transparent and participatory. -- We take a modular and modern approach to software development. -- We build open-source software and open-source process. -- We value ease of implementation. -- Fostering community includes building capacity and making our software and processes accessible to participants with diverse backgrounds and skillsets. -- Data (and data science) is as important as software and process. We build open data sets where possible. -- We strive for transparency for algorithms and places we might be introducing bias. - -## Community Guidelines - -All community members are expected to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). - -Information on contributing to this repository is available in our [Contributing file](CONTRIBUTING.md). - -When participating in gov-codejson open source community conversations and spaces, we ask individuals to follow the following guidelines: - -- When joining a conversation for the first time, please introduce yourself by providing a brief intro that includes: - - your related organization (if applicable) - - your pronouns - - your superpower, and how you hope to use it for gov-codejson -- Embrace a culture of learning, and educate each other. We are all entering this conversation from different starting points and with different backgrounds. There are no dumb questions. -- Take space and give space. We strive to create an equitable environment in which all are welcome and able to participate. We hope individuals feel comfortable voicing their opinions and providing contributions and will do our best to recognize and make space for individuals who may be struggling to find space here. Likewise, we expect individuals to recognize when they are taking up significant space and take a step back to allow room for others. - -- Be respectful. -- Default to positive. Assume others' contributions are legitimate and valuable and that they are made with good intention. - -## Acknowledgements - -This COMMUNITY_GUIDELINES.md was originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions. diff --git a/MAINTAINERS.md b/MAINTAINERS.md deleted file mode 100644 index 43ceb24..0000000 --- a/MAINTAINERS.md +++ /dev/null @@ -1,292 +0,0 @@ -# Maintainers - -This is a list of maintainers for this project. See [CODEOWNERS.md](./CODEOWNERS.md) for list of reviewers for different parts of the codebase. Team members include: - -## Maintainers: - -- @natalialuzuriaga -- @decause-gov - -## Approvers: - -- @natalialuzuriaga -- @decause-gov - -## Reviewers: - -- @IsaacMilarky -- @DinneK -- @sachin-panayil - -| Roles | Responsibilities | Requirements | Defined by | -| -------- | :--------------------------------------------- | :-------------------------------------------------------------------------------- | :---------------------------------------------------------- | -| member | active contributor in the community | multiple contributions to the project. | PROJECT GitHub org Committer Team | -| reviewer | review contributions from other members | history of review and authorship in a sub-project | MAINTAINERS file reviewer entry, and GitHub Org Triage Team | -| approver | approve accepting contributions | highly experienced and active reviewer + contributor to a sub-project | MAINTAINERS file approver entry and GitHub Triage Team | -| lead | set direction and priorities for a sub-project | demonstrated responsibility and excellent technical judgement for the sub-project | MAINTAINERS file owner entry and GitHub Org Admin Team | - -## Contributors - - - -Total number of contributors: - - - - - - - - - - - -
- - natalialuzuriaga -
- Natalia Luzuriaga - - 		- - sachin-panayil -
- Sachin Panayil - - 		- - decause-gov -
- decause-gov - - 		- - cms-eo14168 -
- cms-eo14168 - -
- - -# Tier 3 Release Guidelines - -gov-codejson will see regular updates and new releases. This document describes the general guidelines around how and when a new release is cut. - -## Table of Contents - -- [Versioning](#versioning) - - - [Ongoing version support](#ongoing-version-support) -- [Release Process](#release-process) - - [Goals](#goals) - - [Schedule](#schedule) - - [Communication and Workflow](#communication-and-workflow) - -- [Preparing a Release Candidate](#preparing-a-release-candidate) - - [Incorporating feedback from review](#incorporating-feedback-from-review) -- [Making a Release](#making-a-release) -- [Auto Changelog](#auto-changelog) -- [Hotfix Releases](#hotfix-releases) - -## Versioning - -gov-codejson uses [Semantic Versioning](https://semver.org/). Each release is associated with a [`git tag`](github.com/DSACMS/gov-codejson/tags) of the form `X.Y.Z`. - -Given a version number in the `MAJOR.MINOR.PATCH` (eg., `X.Y.Z`) format, here are the differences in these terms: - -- **MAJOR** version - make breaking/incompatible API changes -- **MINOR** version - add functionality in a backwards compatible manner -- **PATCH** version - make backwards compatible bug fixes - - - - - -### Ongoing version support - - - - - -## Release Process - -The sections below define the release process itself, including timeline, roles, and communication best practices. - -### Goals - - - -. - -### Schedule - - - -### Communication and Workflow - - - - - -## Preparing a Release Candidate - -The following steps outline the process to prepare a Release Candidate of gov-codejson. This process makes public the intention and contents of an upcoming release, while allowing work on the next release to continue as usual in `dev`. - -1. Create a _Release branch_ from the tip of `dev` named `release-x.y.z`, where `x.y.z` is the intended version of the release. This branch will be used to prepare the Release Candidate. For example, to prepare a Release Candidate for `0.5.0`: - - ```bash - git fetch - git checkout origin/dev - git checkout -b release-0.5.0 - git push -u origin release-0.5.0 - ``` - - Changes generated by the steps below should be committed to this branch later. - -2. Create a tag like `x.y.z-rcN` for this Release Candidate. For example, for the first `0.5.0` Release Candidate: - - ```bash - git fetch - git checkout origin/release-0.5.0 - git tag 0.5.0-rc1 - git push --tags - ``` - -3. Publish a [pre-Release in GitHub](proj-releases-new): - - ```md - Tag version: [tag you just pushed] - Target: [release branch] - Release title: [X.Y.Z Release Candidate N] - Description: [copy in ReleaseNotes.md created earlier] - This is a pre-release: Check - ``` - -4. Open a Pull Request to `main` from the release branch (eg. `0.5.0-rc1`). This pull request is where review comments and feedback will be collected. - -5. Conduct Review of the Pull Request that was opened. - -### Incorporating feedback from review - -The review process may result in changes being necessary to the release candidate. - -For example, if the second Release Candidate for `0.5.0` is being prepared, after committing necessary changes, create a tag on the tip of the release branch like `0.5.0-rc2` and make a new [GitHub pre-Release](proj-releases-new) from there: - -```bash -git fetch -git checkout origin/release-0.5.0 -# more commits per OMF review -git tag 0.5.0-rc2 -git push --tags -``` - -Repeat as-needed for subsequent Release Candidates. Note the release branch will be pushed to `dev` at key points in the approval process to ensure the community is working with the latest code. - -## Making a Release - -The following steps describe how to make an approved [Release Candidate](#preparing-a-release-candidate) an official release of gov-codejson: - -1. **Approved**. Ensure review has been completed and approval granted. - -2. **Main**. Merge the Pull Request created during the Release Candidate process to `main` to make the release official. - -3. **Dev**. Open a Pull Request from the release branch to `dev`. Merge this PR to ensure any changes to the Release Candidate during the review process make their way back into `dev`. - -4. **Release**. Publish a [Release in GitHub](proj-releases-new) with the following information - - - Tag version: [X.Y.Z] (note this will create the tag for the `main` branch code when you publish the release) - - Target: main - - Release title: [X.Y.Z] - - Description: copy in Release Notes created earlier - - This is a pre-release: DO NOT check - -5. **Branch**. Finally, keep the release branch and don't delete it. This allows easy access to a browsable spec. - -## Auto Changelog - -It is recommended to use the provided auto changelog github workflow to populate the project’s CHANGELOG.md file: - -```yml -name: Changelog -on: - release: - types: - - created -jobs: - changelog: - runs-on: ubuntu-latest - steps: - - name: "Auto Generate changelog" - uses: heinrichreimer/action-github-changelog-generator@v2.3 - with: - token: ${{{{ secrets.GITHUB_TOKEN }}}} -``` - -This provided workflow will automatically populate the CHANGELOG.md with all of the associated changes created since the last release that are included in the current release. - -This workflow will be triggered when a new release is created. - -If you do not wish to use automatic changelogs, you can delete the workflow and update the CHANGELOG.md file manually. Although, this is not recommended. - -## Hotfix Releases - -In rare cases, a hotfix for a prior release may be required out-of-phase with the normal release cycle. For example, if a critical bug is discovered in the `0.3.x` line after `0.4.0` has already been released. - -1. Create a _Support branch_ from the tag in `main` at which the hotfix is needed. For example if the bug was discovered in `0.3.2`, create a branch from this tag: - - ```bash - git fetch - git checkout 0.3.2 - git checkout -b 0.3.x - git push -u origin 0.3.x - ``` - -2. Merge (or commit directly) the hotfix work into this branch. - -3. Tag the support branch with the hotfix version. For example if `0.3.2` is the version being hotfixed: - - ```bash - git fetch - git checkout 0.3.x - git tag 0.3.3 - git push --tags - ``` - -4. Create a [GitHub Release](proj-releases-new) from this tag and the support branch. For example if `0.3.3` is the new hotfix version: - - ```md - Tag version: 0.3.3 - Target: 0.3.x - Release title: 0.3.3 - Description: [copy in ReleaseNotes created earlier] - This is a pre-release: DO NOT check - ``` - -[proj-releases-new]: https://github.com/DSACMS/gov-codejson/releases/new From c0be2849826fa43f05141562ec71ccd66ef606a4 Mon Sep 17 00:00:00 2001 From: Natalia Luzuriaga Date: Tue, 13 Oct 2026 10:24:57 -0700 Subject: [PATCH 2/8] Update CODEOWNERS.md location Signed-off-by: Natalia Luzuriaga --- .github/CODEOWNERS.md | 11 +++++++++++ CODEOWNERS.md | 9 --------- 2 files changed, 11 insertions(+), 9 deletions(-) create mode 100644 .github/CODEOWNERS.md delete mode 100644 CODEOWNERS.md diff --git a/.github/CODEOWNERS.md b/.github/CODEOWNERS.md new file mode 100644 index 0000000..b9fa34e --- /dev/null +++ b/.github/CODEOWNERS.md @@ -0,0 +1,11 @@ +# Code Owners + +- [@natalialuzuriaga](https://github.com/natalialuzuriaga) +- [@decause-gov](https://github.com/decause-gov) +- [@sachin-panayil](https://github.com/sachin-panayil) +- [@DinneK](https://github.com/DinneK) + +## Repo Domains + +/docs @natalialuzuriaga @decause-gov @sachin-panayil +/schema/ @natalialuzuriaga @decause-gov diff --git a/CODEOWNERS.md b/CODEOWNERS.md deleted file mode 100644 index 8ead0de..0000000 --- a/CODEOWNERS.md +++ /dev/null @@ -1,9 +0,0 @@ -# Code Owners - -- @natalialuzuriaga -- @decause-gov - -## Repo Domains - -/docs @natalialuzuriaga @decause-gov @sachin-panayil -/schema/ @natalialuzuriaga @decause-gov From 9b25e0571919a8ee779ea6183e44e8b7868ac667 Mon Sep 17 00:00:00 2001 From: Natalia Luzuriaga Date: Tue, 13 Oct 2026 10:30:37 -0700 Subject: [PATCH 3/8] Update CONTRIBUTING.md to reflect latest updates Signed-off-by: Natalia Luzuriaga --- CONTRIBUTING.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 17fc112..d5f29dd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -7,19 +7,21 @@ you'll be politely asked to change something. We appreciate all friendly contributions. We encourage you to read this project's CONTRIBUTING policy (you are here), its -[LICENSE](LICENSE.md), and its [README](README.md). +[LICENSE](LICENSE), and its [README](README.md). ## Getting Started -If you would like to comment and provide feedback on the metadata standard, please let us know by filing an **issue on our GitHub repository.** +If you would like to comment and provide feedback on the metadata standard, please let us know by filing an **issue on our GitHub repository**. + +### For agencies We encourage agencies to contribute by [submitting an agency schema addition issue](https://github.com/DSACMS/gov-codejson/issues) to [include their extended schema in the repository](../schemas). This helps foster collaboration and ensures shared improvements benefit the wider community. -For CMS, we are open to adding more fields to CMS code.json for any metadata the agency sees value in collecting. Request new metadata fields by filing a metadata field addition issue [here](https://github.com/DSACMS/gov-codejson/issues/new?template=metadata-field-addition.md). +We are open to adding more fields to maximal schema of government-wide code.json standard for any metadata the government sees value in collecting. Request new metadata fields by filing a metadata field addition issue [here](https://github.com/DSACMS/gov-codejson/issues/new?template=metadata-field-addition.md). ### Team Specific Guidelines -The project is led by the CMS Open Source Program Office team as detailed in [MAINTAINERS.md](/MAINTAINERS.md) +The project is led by the CMS Open Source Program Office team as detailed in [COMMUNITY.md](/COMMUNITY.md). ### Building dependencies @@ -54,7 +56,9 @@ N/A If you would like to comment on the metadata standard, please let us know by filing an **issue on our GitHub repository.** -For CMS, we are open to adding more fields to CMS code.json for any metadata the agency sees value in collecting. Request new metadata fields by filing a metadata field addition issue [here](https://github.com/DSACMS/gov-codejson/issues/new?template=metadata-field-addition.md). +#### For agencies + +We are open to adding more fields to maximal schema of government-wide code.json standard for any metadata the government sees value in collecting. Request new metadata fields by filing a metadata field addition issue [here](https://github.com/DSACMS/gov-codejson/issues/new?template=metadata-field-addition.md). ### Writing Pull Requests @@ -94,7 +98,7 @@ Some important notes regarding the summary line: ## Reviewing Pull Requests -Pull requests will be reviewed by the CMS Open Source Program Office team as detailed in [MAINTAINERS.md](/MAINTAINERS.md) +Pull requests will be reviewed by the CMS Open Source Program Office team as detailed in [COMMUNITY.md](/COMMUNITY.md) ).*?()/$1 '"$CONTRIBUTORS"' $2/' MAINTAINERS.md + echo "Current contributors: $CURRENT" + echo "Existing contributors: $EXISTING" - git config user.name 'github-actions[bot]' - git config user.email 'github-actions[bot]@users.noreply.github.com' - git add MAINTAINERS.md - git commit -m "update contributors count to $CONTRIBUTORS" || exit 0 + if [ "$CURRENT" = "$EXISTING" ]; then + echo "has_changes=false" >> $GITHUB_OUTPUT + echo "No new contributors found. Skipping update!" + else + echo "has_changes=true" >> $GITHUB_OUTPUT + echo "New contributors detected. Running update!" + fi - - name: Push protected - uses: CasperWA/push-protected@v2 + - name: Update contributor list + if: steps.check_changes.outputs.has_changes == 'true' + id: update_contributors + uses: akhilmhdh/contributors-readme-action@v2.3.10 + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} with: - - token: ${{ secrets.PUSH_TO_PROTECTED_BRANCH }} - + readme_path: COMMUNITY.md + commit_message: "updating contributors list" + pr_title_on_protected: "docs: update contributors information" + committer_username: "github-actions[bot]" + committer_email: "github-actions[bot]@users.noreply.github.com" + + - name: Update PR + if: steps.check_changes.outputs.has_changes == 'true' && steps.update_contributors.outputs.pr_id != '' + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + run: | + PR_NUMBER="${{ steps.update_contributors.outputs.pr_id }}" - branch: main \ No newline at end of file + gh pr edit $PR_NUMBER \ + --body "New contributors detected! This PR updates the contributors list in COMMUNITY.md." \ + --add-label "documentation" From bdcd60b5d26646e3daa261457c11f8e8f3c5c273 Mon Sep 17 00:00:00 2001 From: Natalia Luzuriaga Date: Tue, 13 Oct 2026 10:48:58 -0700 Subject: [PATCH 5/8] Update README.md Signed-off-by: Natalia Luzuriaga --- README.md | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/README.md b/README.md index 666e642..f7eb52d 100644 --- a/README.md +++ b/README.md @@ -32,28 +32,28 @@ TODO: Good to include since this is an agency-led project --> ## Core Team -An up-to-date list of core team members can be found in [MAINTAINERS.md](MAINTAINERS.md). At this time, the project is still building the core team and defining roles and responsibilities. We are eagerly seeking individuals who would like to join the community and help us define and fill these roles. - -## Documentation Index - -- [docs](./docs) +An up-to-date list of core team members can be found in [COMMUNITY.md](COMMUNITY.md). ## Repository Structure -##### Documentation - -- [schemas](./schemas) -- [docs](./docs) +``` +. +├── assets # Assets for docs +├── docs # Directory containing information on code.json metadata standard +├── schemas # Schemas for software inventory metadata: code.json, agency extended code.json schemas, and agency-index.json +│ ├── agency-index # Schema for agency index +│ └── cms # CMS code.json extended agency schema +└── tests # JSON schema validation tests + └── examples # Examples of completed code.jsons +``` -##### Files +### Documentation Index -- [CONTRIBUTING.md](./CONTRIBUTING.md) -- [MAINTAINERS.md](./MAINTAINERS.md) -- [CODEOWNERS.md](./CODEOWNERS.md) -- [COMMUNITY_GUIDELINES.md](./COMMUNITY_GUIDELINES.md) -- [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md) -- [SECURITY.md](./SECURITY.md) -- [LICENSE](./LICENSE) +- [CONTRIBUTING.md](./CONTRIBUTING.md): Guidelines for contributing to the project +- [COMMUNITY.md](./COMMUNITY.md) & [CODEOWNERS.md](./.github/CODEOWNERS.md): Core team information and guidelines for community participation +- [GOVERNANCE.md](./GOVERNANCE.md) - Project governance information +- [SECURITY.md](./SECURITY.md) - Security and vulnerability disclosure policies +- [LICENSE](./LICENSE) - CC0 1.0 Universal public domain dedication # Development and Software Delivery Lifecycle @@ -91,7 +91,7 @@ Thank you for considering contributing to an Open Source project of the US Gover ## Codeowners -The contents of this repository are managed by the CMS Open Source Program Office. Those responsible for the code and documentation in this repository can be found in [CODEOWNERS.md](CODEOWNERS.md). +The contents of this repository are managed by the CMS Open Source Program Office. Those responsible for the code and documentation in this repository can be found in [CODEOWNERS.md](./github/CODEOWNERS.md). ## Community @@ -103,7 +103,7 @@ We also recognize capacity building as a key part of involving a diverse open so ### Community Guidelines -Principles and guidelines for participating in our open source community are can be found in [COMMUNITY_GUIDELINES.md](COMMUNITY_GUIDELINES.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events. +Principles and guidelines for participating in our open source community are can be found in [COMMUNITY.md](COMMUNITY.md). Please read them before joining or starting a conversation in this repo or one of the channels listed below. All community members and participants are expected to adhere to the community guidelines and code of conduct when participating in community spaces including: code repositories, communication channels and venues, and events. -This project is governed by our [Community Guidelines](COMMUNITY_GUIDELINES.md) and [Code of Conduct](CODE_OF_CONDUCT.md). +This project is governed by our [Community Guidelines](COMMUNITY.md) and [Code of Conduct](CODE_OF_CONDUCT.md). From 012c637bac639b00ebaeb4b6a981ba1d3029204d Mon Sep 17 00:00:00 2001 From: Natalia Luzuriaga Date: Tue, 13 Oct 2026 10:57:11 -0700 Subject: [PATCH 8/8] Update workflows specifying permission type Signed-off-by: Natalia Luzuriaga --- .github/workflows/auto-changelog.yml | 4 +-- .github/workflows/gitleaks.yml | 11 ++++---- .github/workflows/repoHygieneCheck.yml | 39 +++++++++++--------------- 3 files changed, 25 insertions(+), 29 deletions(-) diff --git a/.github/workflows/auto-changelog.yml b/.github/workflows/auto-changelog.yml index b406d84..fc53c09 100644 --- a/.github/workflows/auto-changelog.yml +++ b/.github/workflows/auto-changelog.yml @@ -3,6 +3,8 @@ on: release: types: - created +permissions: + contents: write jobs: changelog: runs-on: ubuntu-latest @@ -10,6 +12,4 @@ jobs: - name: "Auto Generate changelog" uses: heinrichreimer/action-github-changelog-generator@v2.3 with: - token: ${{ secrets.GITHUB_TOKEN }} - \ No newline at end of file diff --git a/.github/workflows/gitleaks.yml b/.github/workflows/gitleaks.yml index 94ae3f0..71b04d7 100644 --- a/.github/workflows/gitleaks.yml +++ b/.github/workflows/gitleaks.yml @@ -1,15 +1,16 @@ name: Check for Secrets on: - pull_request: - push: - + pull_request: + push: +permissions: + contents: read jobs: scan-for-secrets: name: Run gitleaks runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - with: {fetch-depth: 0} + with: { fetch-depth: 0 } - name: Check for GitLeaks - uses: gacts/gitleaks@v1 \ No newline at end of file + uses: gacts/gitleaks@v1 diff --git a/.github/workflows/repoHygieneCheck.yml b/.github/workflows/repoHygieneCheck.yml index 41180b1..6c3a85e 100644 --- a/.github/workflows/repoHygieneCheck.yml +++ b/.github/workflows/repoHygieneCheck.yml @@ -2,7 +2,7 @@ name: "Repository Hygiene Check" on: push: branches: - - 'main' + - "main" workflow_dispatch: jobs: @@ -10,9 +10,8 @@ jobs: name: Check For First Run runs-on: ubuntu-latest outputs: - should_run: ${{ steps.check.outputs.should_run }} - + permissions: contents: read pull-requests: write @@ -21,13 +20,13 @@ jobs: - id: check run: | # If manually triggered, always run - + if [[ "${{ github.event_name }}" == "workflow_dispatch" ]]; then - + echo "should_run=true" >> $GITHUB_OUTPUT exit 0 fi - + # Check if initialization label exists has_label=$(gh label list --json name | jq '.[] | select(.name=="repolinter-initialized")') @@ -39,42 +38,38 @@ jobs: echo "should_run=false" >> $GITHUB_OUTPUT fi env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - resolve-repolinter-json: name: Get Repolinter Config needs: check-first-run - if: needs.check-first-run.outputs.should_run == 'true' - + permissions: + contents: read uses: DSACMS/repo-scaffolder/.github/workflows/extendJSONFile.yml@main - with: - url_to_json: 'https://raw.githubusercontent.com/DSACMS/repo-scaffolder/main/tier3/%7B%7Bcookiecutter.project_slug%7D%7D/repolinter.json' - + with: + url_to_json: "https://raw.githubusercontent.com/DSACMS/repo-scaffolder/main/tier3/%7B%7Bcookiecutter.project_slug%7D%7D/repolinter.json" + repolinter-checks: name: Tier 3 Checks needs: [check-first-run, resolve-repolinter-json] - + if: needs.check-first-run.outputs.should_run == 'true' - + runs-on: ubuntu-latest permissions: contents: write pull-requests: write env: - RAW_JSON: ${{ needs.resolve-repolinter-json.outputs.raw-json }} - + steps: - uses: actions/checkout@v4 - run: echo $RAW_JSON > repolinter.json - uses: DSACMS/repolinter-action@main with: - config_file: 'repolinter.json' - output_type: 'pull-request' - pull_request_labels: 'repolinter-initialized, cms-oss, cms-gov' - + config_file: "repolinter.json" + output_type: "pull-request" + pull_request_labels: "repolinter-initialized, cms-oss, cms-gov" + token: ${{ secrets.REPOLINTER_AUTO_TOKEN }} - \ No newline at end of file