Skip to content

Refactor configmap documentation#2535

Merged
theakshaypant merged 2 commits intotektoncd:mainfrom
chmouel:refactor-configmap-documentation
Mar 5, 2026
Merged

Refactor configmap documentation#2535
theakshaypant merged 2 commits intotektoncd:mainfrom
chmouel:refactor-configmap-documentation

Conversation

@chmouel
Copy link
Copy Markdown
Member

@chmouel chmouel commented Mar 4, 2026

📝 Description of the Change

Consolidated scattered configuration documentation into a unified reference guide. This refactoring improves discoverability and reduces duplication by creating a centralized ConfigMap API reference while simplifying operations pages to focus on high-level concepts.

Key Changes:

  • Created centralized ConfigMap reference in docs/content/docs/api/configmap.md with all configuration parameters and anchors
  • Simplified operations pages:
    • docs/content/docs/operations/configuration.md (removed 416 lines of duplicate parameter listings)
    • docs/content/docs/operations/settings.md (removed 332 lines of duplicate parameter listings)
  • Updated internal links across 5 documentation files to point to configuration anchors for proper cross-referencing
  • Added project logo to README.md for visual identity
image

Benefits:

Users can now find all configuration parameters in one authoritative location with proper anchors for linking, while operations pages provide clearer, more maintainable high-level guidance.

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

  • Not Applicable

🤖 AI Assistance

  • I have not used any AI assistance for this PR.
  • I have used AI assistance for this PR.

If you have used AI assistance, please provide the following details:

Which LLM was used?

  • GitHub Copilot
  • ChatGPT (OpenAI)
  • Claude (Anthropic)
  • Cursor
  • Gemini (Google)
  • Other: ____________

Extent of AI Assistance:

  • Documentation and research only
  • Code generation (parts of the code)
  • Full code generation (most of the PR)
  • PR description and comments
  • Commit message(s)

Important

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Gemini gemini@google.com
Co-authored-by: ChatGPT noreply@chatgpt.com
Co-authored-by: Claude noreply@anthropic.com
Co-authored-by: Cursor noreply@cursor.com
Co-authored-by: Copilot Copilot@users.noreply.github.com

**💡You can use the script ./hack/add-llm-coauthor.sh to automatically add
these co-author trailers to your commits.

✅ Submitter Checklist

  • 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
  • ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
  • ♽ I have run make test and make lint locally to check for and fix any issues. For an efficient workflow, I have considered installing pre-commit and running pre-commit install to automate these checks.
  • 📖 I have added or updated documentation for any user-facing changes.
  • 🧪 I have added sufficient unit tests for my code changes.
  • 🎁 I have added end-to-end tests where feasible. See README for more details.
  • 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
  • If adding a provider feature, I have filled in the following and updated the provider documentation:
    • GitHub App
    • GitHub Webhook
    • Gitea/Forgejo
    • GitLab
    • Bitbucket Cloud
    • Bitbucket Data Center

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refactors the Pipelines-as-Code documentation to improve clarity and maintainability. The primary goal was to centralize all configuration parameter details into a dedicated API guide, allowing other documentation pages to focus on conceptual explanations and operational tasks. This change enhances the user experience by providing a single, comprehensive source for configuration parameters and ensures consistency across the documentation.

Highlights

  • Documentation Refactoring: All configuration parameter references have been consolidated into a new central API guide, streamlining the documentation structure.
  • Simplified Operations Pages: Operations pages have been simplified to focus on high-level concepts and inheritance, removing exhaustive field lists that are now in the API guide.
  • Internal Link Updates: Numerous internal links across the documentation have been updated to correctly point to the new centralized configuration references.
  • README Enhancement: A Pipelines-as-Code logo has been added to the main README file for improved branding.
Changelog
  • README.md
    • Added a logo image to the main README.
  • docs/content/docs/advanced/cleanup.md
    • Updated the link for global cleanup settings to point to the new ConfigMap API reference.
  • docs/content/docs/api/configmap.md
    • Added introductory text for retention policies.
    • Added a comprehensive 'See Also' section with links to related configuration topics.
  • docs/content/docs/guides/creating-pipelines/github-token.md
    • Updated the link for GitHub App token configuration to the new ConfigMap API reference.
  • docs/content/docs/guides/pipeline-resolution/_index.md
    • Clarified the page's scope to the task annotation.
    • Updated links for custom hub support and token scoping to the new ConfigMap API reference.
  • docs/content/docs/guides/pipeline-resolution/remote-pipelines.md
    • Clarified the page's scope to the pipeline annotation.
    • Updated the link for custom hub support to the new ConfigMap API reference.
  • docs/content/docs/installation/openshift.md
    • Updated the link for custom hub catalogs to the new ConfigMap API reference.
  • docs/content/docs/operations/configuration.md
    • Refactored the page to remove the extensive configuration reference.
    • Replaced detailed configuration options with a brief overview and a link to the new ConfigMap API reference.
  • docs/content/docs/operations/settings.md
    • Rewrote the page to provide a high-level overview of configuration layers (global vs. per-repository).
    • Linked to the new ConfigMap and Repository CR settings API references.
Activity
  • No specific activity (comments, reviews, progress updates) was provided in the context.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request is a significant refactoring of the configuration documentation, consolidating parameter references into a central API guide and simplifying the operations pages. The changes greatly improve the structure and navigability of the documentation. I have one suggestion to improve link consistency in the new 'See Also' section for better long-term maintainability.

Note: Security Review has been skipped due to the limited scope of the PR.

@chmouel chmouel force-pushed the refactor-configmap-documentation branch from 3e79ab6 to 2df0eec Compare March 4, 2026 21:59
chmouel added 2 commits March 4, 2026 23:14
Consolidated configuration parameter references into a central API
guide. Simplified the operations pages to focus on high-level
concepts or inheritance instead of exhaustive field lists. Updated
internal links to target specific configuration anchors.

Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Included the Pipelines-as-Code project logo in the header to improve
brand visibility and visual identification for new users.

And rephrase a bit the README for upstream preparation.

Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
@chmouel chmouel force-pushed the refactor-configmap-documentation branch from 2df0eec to 428d52e Compare March 4, 2026 22:14
@theakshaypant theakshaypant merged commit b0864df into tektoncd:main Mar 5, 2026
@chmouel chmouel deleted the refactor-configmap-documentation branch March 5, 2026 06:53
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.

2 participants