Skip to content

Add new workflow for detecting changes in dot org #854

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

lamATnginx
Copy link
Contributor

Proposed changes

Closes https://github.com/nginxinc/docs-platform/issues/548

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

  • I have read the contributing guidelines
  • I have signed the F5 Contributor License Agreement (CLA)
  • I have rebased my branch onto main
  • I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
  • I have ensured that the commit messages adhere to Conventional Commits
  • I have ensured that documentation content adheres to the style guide
  • If the change involves potentially sensitive changes1, I have assessed the possible impact
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • I have ensured that existing tests pass after adding my changes
  • If applicable, I have updated README.md

Footnotes

  1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content.

@lamATnginx lamATnginx self-assigned this Jul 18, 2025
@lamATnginx lamATnginx added the enhancement New feature or request label Jul 18, 2025
@github-actions github-actions bot added the tooling Back end, repository, Hugo, and all things not related to content label Jul 18, 2025
Comment on lines 18 to 34
name: Detect changes in 'en' docs of nginx/nginx.org
runs-on: ubuntu-latest
outputs:
IS_CHANGES_DETECTED: ${{ steps.check_changes.outputs.changed }}
steps:
- name: PLACEHOLDER
id: check_changes
run: |
echo "PLACEHOLDER"

execute-make:

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: {}
Copy link

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/docs/854/

Comment on lines +36 to +44
name: Execute make target 'make hugo-md'
if: needs.detect-changes.outputs.IS_CHANGES_DETECTED
needs: detect-changes
runs-on: ubuntu-latest
steps:
- name: PLACEHOLDER
run: |
echo "PLACEHOLDER"

move-generated-files:

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: {}
Comment on lines +46 to +54
name: Move generated markdown files to '/content/nginx' directory
if: needs.detect-changes.outputs.IS_CHANGES_DETECTED
needs: execute-make
runs-on: ubuntu-latest
steps:
- name: PLACEHOLDER
run: |
echo "PLACEHOLDER"

create-PR:

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: {}
Comment on lines +56 to +62
name: Create PR in documentation repository
if: needs.detect-changes.outputs.IS_CHANGES_DETECTED
needs: move-generated-files
runs-on: ubuntu-latest
steps:
- name: PLACEHOLDER
run: |
echo "PLACEHOLDER"

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: {}
@lamATnginx lamATnginx force-pushed the dot-org-changes branch 3 times, most recently from bff500c to 303b5f4 Compare July 18, 2025 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tooling Back end, repository, Hugo, and all things not related to content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant