Skip to content

Conversation

@lamATnginx
Copy link
Contributor

@lamATnginx lamATnginx commented Jul 18, 2025

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
@github-actions
Copy link

Deploy Preview will be available once build job completes!

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

@lamATnginx lamATnginx force-pushed the dot-org-changes branch 23 times, most recently from d130cd2 to d19ec25 Compare July 21, 2025 21:42
@lamATnginx lamATnginx marked this pull request as ready for review July 21, 2025 21:47
@lamATnginx lamATnginx requested a review from a team as a code owner July 21, 2025 21:47
Copy link
Member

@ADubhlaoich ADubhlaoich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved: please avoid linking to issues in closed, internal repositories.

If you want to create a logical link between an issue and a PR, you can do so from the sidebar of the issue.

@ADubhlaoich ADubhlaoich merged commit bef41ba into main Aug 11, 2025
10 checks passed
@ADubhlaoich ADubhlaoich deleted the dot-org-changes branch August 11, 2025 12:21
salonichf5 pushed a commit to salonichf5/documentation that referenced this pull request Aug 11, 2025
* feat: Add new workflow for detecting changes in dot org
* Refactor to use a new dep for making PR
* Use better change comparision command to detect changes
* Added paths to git add the generated files + yaml

---------

Co-authored-by: Michael McKeen <[email protected]>
@lamATnginx lamATnginx restored the dot-org-changes branch September 22, 2025 16:31
lamATnginx added a commit that referenced this pull request Sep 22, 2025
@lamATnginx lamATnginx mentioned this pull request Sep 22, 2025
5 tasks
lamATnginx added a commit that referenced this pull request Sep 22, 2025
chore: Revert PR #854
@ADubhlaoich ADubhlaoich deleted the dot-org-changes branch November 26, 2025 12:31
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.

5 participants