Skip to content

docs: consolidate code hosting setup instructions#19202

Open
nijel wants to merge 1 commit intoWeblateOrg:mainfrom
nijel:vcs-docs
Open

docs: consolidate code hosting setup instructions#19202
nijel wants to merge 1 commit intoWeblateOrg:mainfrom
nijel:vcs-docs

Conversation

@nijel
Copy link
Copy Markdown
Member

@nijel nijel commented Apr 23, 2026

Move scattered pieces to a single location.

Fixes #16257

@nijel nijel added this to the 5.17.1 milestone Apr 23, 2026
@nijel nijel requested review from AliceVisek and Copilot April 23, 2026 15:33
@nijel nijel self-assigned this Apr 23, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Consolidates provider-specific code hosting integration guidance (repo access, notifications, and push/PR workflows) into a single administrator-facing documentation page, and updates existing docs to link to it (Fixes #16257).

Changes:

  • Added a new provider-oriented admin doc page: /admin/code-hosting.
  • Replaced scattered provider-specific setup sections in existing docs with concise pointers to the new page.
  • Added the new page to the docs index and noted it in the changelog.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
docs/admin/code-hosting.rst New consolidated provider checklist for GitHub/GitLab/Gitea/Bitbucket/Azure/Pagure/etc.
docs/vcs.rst Replaces provider-specific sections with links to the consolidated page.
docs/admin/continuous.rst Replaces webhook/app setup blocks with a pointer to the consolidated page.
docs/admin/config.rst Adds a cross-link from credential settings to the consolidated page.
docs/index.rst Adds the new page to the Administrator docs toctree.
docs/changes.rst Mentions the new documentation page in the 5.17.1 notes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/vcs.rst
Comment thread docs/admin/continuous.rst
Comment thread docs/admin/code-hosting.rst Outdated
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b87d40f7e7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/admin/continuous.rst
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@argos-ci
Copy link
Copy Markdown

argos-ci Bot commented Apr 23, 2026

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ⚠️ Changes detected (Review) 21 changed May 6, 2026, 4:01 PM

@nijel nijel requested a review from orangesunny April 24, 2026 08:08
@nijel nijel modified the milestones: 5.17.1, 5.18 Apr 29, 2026
Move scattered pieces to a single location.

Fixes WeblateOrg#16257
@chatgpt-codex-connector
Copy link
Copy Markdown

💡 Codex Review

* Added Forgejo notification webhook, see :ref:`Forgejo notifications <code-hosting-forgejo-notifications>`.

P2 Badge Restore released changelog wording

This edits the already released Weblate 5.17 changelog section, which conflicts with the repository guidance in AGENTS.md to avoid altering changelog sections for released versions. The old forgejo-setup anchor is still preserved in docs/admin/continuous.rst, so this historical entry does not need to be rewritten and the change only creates unnecessary churn in released documentation/translations; please keep released entries unchanged and limit the new changelog entry to the current unreleased section.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@AliceVisek
Copy link
Copy Markdown
Contributor

I think it would be also beneficial to include how to push changes from Weblate, especially the table there (now available at https://docs.weblate.org/en/latest/admin/continuous.html#pushing-changes-from-weblate ).

I am not sure where to place it, though. Either after the Setup overview or at the very bottom? Or should it be referenced in each VCS section? What does @orangesunny think?

Comment on lines +102 to +103
:guilabel:`Webhook` in GitHub. It does not by itself grant Hosted Weblate write
access to the repository, though. To push changes back, you still need to add
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
:guilabel:`Webhook` in GitHub. It does not by itself grant Hosted Weblate write
access to the repository, though. To push changes back, you still need to add
:guilabel:`Webhook` in GitHub. However, it does not by itself grant Hosted Weblate write
access to the repository. To push changes back, you still need to add

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.

Version control integration documentation

3 participants