Update repository URLs to pulp org

[daviddavis]

The repository moved to https://github.com/pulp/pulp_workflow. This updates the repository/bug-tracker links, docs, release instructions, changelog issue links, CI scripts, and the plugin template github_org.

Assisted-by: GitHub Copilot (Claude Opus 4.8)

[Copilot]

Pull request overview

Updates repository metadata and documentation to reflect the move of pulp_workflow to the pulp GitHub organization, ensuring links and generated CI/docs artifacts reference the new canonical location.

Changes:

• Updated plugin-template configuration (github_org) to pulp.
• Updated repository, bug tracker, and changelog issue links to https://github.com/pulp/pulp_workflow.
• Updated release/docs/CI script references to the new org/repo URLs.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
template_config.yml	Switches github_org to pulp for plugin-template generation.
releasing.md	Updates GitHub Actions workflow links to the pulp/pulp_workflow repository.
README.md	Updates documentation links pointing into this repository under the pulp org.
pyproject.toml	Updates project.urls and towncrier issue link format to the new repo location.
CHANGES.md	Updates issue links to the new GitHub org/repo.
.github/workflows/scripts/update_backport_labels.py	Updates GitHub API endpoints to target pulp/pulp_workflow.
.github/workflows/scripts/build_python_client.sh	Updates generated docs metadata (repo_name/repo_url) to the new repo location.

---

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

[Copilot]

Pull request overview

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

[patchback]

Backport to 0.2: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply adfb339 on top of patchback/backports/0.2/adfb33940f3bd4b17c12b0fca184045d19babe22/pr-40

Backporting merged PR #40 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulp_workflow.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/0.2/adfb33940f3bd4b17c12b0fca184045d19babe22/pr-40 upstream/0.2

4. Now, cherry-pick PR Update repository URLs to pulp org #40 contents into that branch:

   $ git cherry-pick -x adfb33940f3bd4b17c12b0fca184045d19babe22

   If it'll yell at you with something like fatal: Commit adfb33940f3bd4b17c12b0fca184045d19babe22 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x adfb33940f3bd4b17c12b0fca184045d19babe22

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Update repository URLs to pulp org #40 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/0.2/adfb33940f3bd4b17c12b0fca184045d19babe22/pr-40

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.