Skip to content

Conversation

@GeorgeWestwater
Copy link
Contributor

This PR contains updates to the OSS practices and policies documentation, including:

  • Open-core policy updates
  • Community meetings and CAC documentation
  • Formatting improvements and cleanup
  • Trademark guidelines clarifications
  • Project membership and governance updates
  • Header formatting consistency for MkDocs

Please review the changes and provide feedback.

GeorgeWestwater and others added 27 commits June 13, 2025 06:29
…e; changing reference from "project owners" to advisors.
… terms with respect to Decider and Community Organizers.
…onvey any rights over trademarks or logo marks.
…ss of whether the downstream distriution is commercialized or offered for free use.
@GeorgeWestwater GeorgeWestwater requested review from a team as code owners September 17, 2025 13:09
@GeorgeWestwater GeorgeWestwater requested a review from a team as a code owner September 17, 2025 13:09
Comment on lines +10 to +23
name: Deploy docs
runs-on: ubuntu-latest
steps:
- name: Checkout master
uses: actions/checkout@v1

- name: Deploy docs
uses: mhausenblas/mkdocs-deploy-gh-pages@master
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
CONFIG_FILE: mkdocs.yml
#EXTRA_PACKAGES: build-base
# GITHUB_DOMAIN: github.myenterprise.com
REQUIREMENTS: /requirements.txt No newline at end of file

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}

Copilot Autofix

AI 4 months ago

The best way to fix the problem is to add a permissions block to the workflow, either at the root level (applying to all jobs), or at the job-level (applying only to build). For minimal change and clarity, add it just above the build job if you only want it affecting this job. For deploying to GitHub Pages, the deployment action (mkdocs-deploy-gh-pages) almost always needs contents: write permission to push the generated documentation to the gh-pages branch. Therefore, the permissions block should be:

permissions:
  contents: write

Insert this block either at the top level (just under name/on), or indented under the build: job (best practice: put it at the job level to scope it tightly). So in this snippet, add under line 9, before line 10, properly indented.

Suggested changeset 1
.github/workflows/publish.yml

Autofix patch

Autofix patch
Run the following command in your local git repository to apply this patch
cat << 'EOF' | git apply
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -7,6 +7,8 @@
 
 jobs:
   build:
+    permissions:
+      contents: write
     name: Deploy docs
     runs-on: ubuntu-latest
     steps:
EOF
@@ -7,6 +7,8 @@

jobs:
build:
permissions:
contents: write
name: Deploy docs
runs-on: ubuntu-latest
steps:
Copilot is powered by AI and may make mistakes. Always verify output.
@GeorgeWestwater GeorgeWestwater merged commit 638ac33 into main Sep 17, 2025
5 of 6 checks passed
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.

3 participants