{"id":75882,"date":"2026-05-14T07:08:01","date_gmt":"2026-05-14T07:08:01","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=75882"},"modified":"2026-05-14T07:08:04","modified_gmt":"2026-05-14T07:08:04","slug":"master-guide-how-to-link-github-issues-commits-branches-and-pull-requests-same-repo-and-cross-repo-workflow","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/master-guide-how-to-link-github-issues-commits-branches-and-pull-requests-same-repo-and-cross-repo-workflow\/","title":{"rendered":"Master Guide: How to Link GitHub Issues, Commits, Branches, and Pull Requests \u2014 Same Repo and Cross-Repo Workflow"},"content":{"rendered":"\n

1. Introduction<\/h2>\n\n\n\n

In many teams, GitHub Issues, commits, branches, and pull requests are created in the same repository<\/strong>. That is the simple case.<\/p>\n\n\n\n

But your setup is more advanced and very common in real companies:<\/p>\n\n\n

Central task\/ticket repo:\ndevops-school-com\/TaskManager\n\nCode repos:\ndevops-school-com\/frontend-repo\ndevops-school-com\/backend-repo\ndevops-school-com\/mobile-repo\n<\/code><\/span><\/pre>\n\n\n
Your ticket is maintained here:<\/p>\n\n\n
devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
But the actual code changes may happen in other repositories.<\/p>\n\n\n\n
So the goal is:<\/p>\n\n\n
TaskManager<\/span> issue<\/span> #560<\/span>\n        \u2193\nlinked<\/span> with<\/span> branches<\/span>\n        \u2193\nlinked<\/span> with<\/span> commits<\/span>\n        \u2193\nlinked<\/span> with<\/span> pull<\/span> requests<\/span>\n        \u2193\ntracked<\/span> across<\/span> multiple<\/span> repositories<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
GitHub supports this through issue\/PR references, closing keywords, commit message references, manual Development sidebar linking, and automation. GitHub automatically converts references to issues, pull requests, and commits into links in GitHub conversations and Markdown areas such as issue bodies, PR bodies, and comments. (GitHub Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
2. Important GitHub Concepts<\/h1>\n\n\n\n
2.1 Issue<\/h2>\n\n\n\n
An Issue<\/strong> is usually used for a task, bug, feature request, or work item.<\/p>\n\n\n\n
Example:<\/p>\n\n\n
devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
In your case, this is the central ticket.<\/p>\n\n\n\n
\n\n\n\n
2.2 Commit<\/h2>\n\n\n\n
A commit<\/strong> is an actual code change.<\/p>\n\n\n\n
Example:<\/p>\n\n\n
git commit -m \"Add login validation for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
This message links the commit to the central TaskManager issue.<\/p>\n\n\n\n
\n\n\n\n
2.3 Branch<\/h2>\n\n\n\n
A branch<\/strong> is where a developer works before creating a PR.<\/p>\n\n\n\n
Example:<\/p>\n\n\n
git checkout -b task-560-add-login-validation\n<\/code><\/span><\/pre>\n\n\n
Branch names do not automatically close or update issues, but good branch naming helps traceability.<\/p>\n\n\n\n
\n\n\n\n
2.4 Pull Request<\/h2>\n\n\n\n
A Pull Request<\/strong> is the review and merge request for code changes.<\/p>\n\n\n\n
Example PR title:<\/p>\n\n\n
[Task #560]<\/span> Add<\/span> login<\/span> validation<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Example PR body:<\/p>\n\n\n
Related to devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
or:<\/p>\n\n\n
Closes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
GitHub can link a PR to an issue manually or by using supported keywords in the PR description. When a linked PR is merged into the default branch, GitHub can automatically close the linked issue. (GitHub Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
3. Same-Repository Linking<\/h1>\n\n\n\n
This is the simplest case.<\/p>\n\n\n\n
Assume your issue and code are in the same repository:<\/p>\n\n\n
Repository:\ndevops-school-com\/backend-repo\n\nIssue:\ndevops-school-com\/backend-repo#25<\/span>\n\nPR:\ndevops-school-com\/backend-repo#30<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
3.1 Referencing an Issue in a Commit Message<\/h2>\n\n\n
git commit -m \"Add payment validation for #25\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
This creates a reference to issue #25<\/code>.<\/p>\n\n\n\n
Better commit message:<\/p>\n\n\n
git<\/span> commit<\/span> -m<\/span> \"Add<\/span> payment<\/span> validation<\/span>\n\nRelated<\/span> to<\/span> #25<\/span>\"\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
3.2 Referencing an Issue in a PR Body<\/h2>\n\n\n
## Task<\/span>\n\nRelated to #25<\/span>\n\n## What changed?<\/span>\n\n- Added payment validation\n- Updated API response\n- Added validation tests\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This creates a clickable link from the PR to the issue.<\/p>\n\n\n\n
3.3 Auto-Closing Same-Repo Issue from PR<\/h2>\n\n\n\n
Use one of GitHub\u2019s closing keywords:<\/p>\n\n\n
Closes<\/span> #25<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
or:<\/p>\n\n\n
Fixes<\/span> #25<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
or:<\/p>\n\n\n
Resolves<\/span> #25<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Supported keywords include close<\/code>, closes<\/code>, closed<\/code>, fix<\/code>, fixes<\/code>, fixed<\/code>, resolve<\/code>, resolves<\/code>, and resolved<\/code>. GitHub also supports uppercase and colon variants such as CLOSES: #10<\/code>. (GitHub Docs<\/a>)<\/p>\n\n\n\n
Example PR body:<\/p>\n\n\n
## Task<\/span>\n\nCloses #25<\/span>\n\n## Summary<\/span>\n\n- Added payment validation\n- Added backend validation test cases\n- Updated error message\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
4. Cross-Repository Linking: Your Real Scenario<\/h1>\n\n\n\n
Your case:<\/p>\n\n\n
Central issue repo:\ndevops-school-com\/TaskManager\n\nIssue:\ndevops-school-com\/TaskManager#560<\/span>\n\nCode repo:\ndevops-school-com\/backend-repo\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
In this case, do not<\/strong> use only:<\/p>\n\n\n
#560<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Because #560<\/code> inside backend-repo<\/code> means:<\/p>\n\n\n
devops-school-com\/backend-repo#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
That is not your TaskManager issue.<\/p>\n\n\n\n
You must use the full cross-repo reference:<\/p>\n\n\n
devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
5. Correct Cross-Repo Commit Message Examples<\/h1>\n\n\n\n
5.1 Simple Commit Reference<\/h2>\n\n\n
git commit -m \"Add login validation for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
5.2 Better Multi-Line Commit Message<\/h2>\n\n\n
git commit -m \"Add login validation\n\nRelated to devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
5.3 Feature Commit<\/h2>\n\n\n
git commit -m \"Implement vehicle search filters for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
5.4 Bug Fix Commit<\/h2>\n\n\n
git commit -m \"Fix empty response handling for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
5.5 UI Commit<\/h2>\n\n\n
git commit -m \"Update dashboard card layout for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
5.6 API Commit<\/h2>\n\n\n
git commit -m \"Add organization task API for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
5.7 Test Commit<\/h2>\n\n\n
git commit -m \"Add unit tests for task filtering related to devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
5.8 Documentation Commit<\/h2>\n\n\n
git commit -m \"Update setup guide for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
6. Cross-Repo PR Description Examples<\/h1>\n\n\n\n
6.1 Safe Linking Without Auto-Close<\/h2>\n\n\n\n
Use this for most PRs:<\/p>\n\n\n
## Task<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Added backend validation\n- Updated API response structure\n- Added test coverage\n\n## Testing done<\/span>\n\n- Ran unit tests\n- Tested API manually\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This creates traceability but does not auto-close the issue.<\/p>\n\n\n\n
\n\n\n\n
6.2 Auto-Close Cross-Repo Issue<\/h2>\n\n\n\n
Use this only when this PR fully completes the task:<\/p>\n\n\n
## Task<\/span>\n\nCloses devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Completed backend implementation\n- Added frontend integration\n- Added test coverage\n\n## Testing done<\/span>\n\n- Verified locally\n- Tested staging deployment\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
For issues in a different repository, GitHub\u2019s documented syntax is:<\/p>\n\n\n
KEYWORD OWNER\/REPOSITORY#ISSUE-NUMBER<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Example:<\/p>\n\n\n
Fixes octo-org\/octo-repo#100<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
For your case:<\/p>\n\n\n
Fixes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
(GitHub Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
7. Very Important: Related to<\/code> vs Closes<\/code><\/h1>\n\n\n\n
This is where many teams get confused.<\/p>\n\n\n\n
Keyword<\/th>Meaning<\/th>Auto-closes issue?<\/th>Best use<\/th><\/tr><\/thead>
Related to devops-school-com\/TaskManager#560<\/code><\/td>Simple link\/reference<\/td>No<\/td>Normal multi-repo work<\/td><\/tr>
Refs devops-school-com\/TaskManager#560<\/code><\/td>Simple reference<\/td>No<\/td>Optional style<\/td><\/tr>
Fixes devops-school-com\/TaskManager#560<\/code><\/td>Final fix<\/td>Yes, after merge to default branch<\/td>Final PR<\/td><\/tr>
Closes devops-school-com\/TaskManager#560<\/code><\/td>Final closure<\/td>Yes, after merge to default branch<\/td>Final PR<\/td><\/tr>
Resolves devops-school-com\/TaskManager#560<\/code><\/td>Final resolution<\/td>Yes, after merge to default branch<\/td>Final PR<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
For your 4-repo setup, use Related to<\/code> in most PRs. Use Closes<\/code>, Fixes<\/code>, or Resolves<\/code> only in the PR that truly completes the TaskManager issue.<\/p>\n\n\n\n
Example:<\/p>\n\n\n
frontend-repo PR: Related to devops-school-com\/TaskManager#560<\/span>\nbackend-repo PR: Related to devops-school-com\/TaskManager#560<\/span>\nmobile-repo PR: Closes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Why? Because if you use Closes<\/code> in the first PR, GitHub may close the central TaskManager issue too early after that PR is merged.<\/p>\n\n\n\n
\n\n\n\n
8. Branch Naming Standard<\/h1>\n\n\n\n
Branch names are for humans and team discipline. GitHub does not automatically close issues just because of a branch name, but a good branch name makes everything easier.<\/p>\n\n\n\n
Recommended format:<\/p>\n\n\n
task-560-short-description\n<\/code><\/span><\/pre>\n\n\n
Examples:<\/p>\n\n\n
git checkout -b task-560-add-login-validation\n<\/code><\/span><\/pre>\n\n
git checkout -b task-560-fix-vehicle-filter\n<\/code><\/span><\/pre>\n\n
git checkout -b task-560-update-dashboard-ui\n<\/code><\/span><\/pre>\n\n\n
For larger teams, use repo prefix:<\/p>\n\n\n
git checkout -b tm-560-backend-login-validation\n<\/code><\/span><\/pre>\n\n\n
or:<\/p>\n\n\n
git checkout -b taskmanager-560-api-filter-fix\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
9. PR Title Standard<\/h1>\n\n\n\n
Recommended PR title:<\/p>\n\n\n
[Task #560]<\/span> Add<\/span> login<\/span> validation<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
Examples:<\/p>\n\n\n
[Task #560]<\/span> Add<\/span> vehicle<\/span> search<\/span> filters<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n
[Task #560]<\/span> Fix<\/span> dashboard<\/span> loading<\/span> issue<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n
[Task #560]<\/span> Add<\/span> backend<\/span> API<\/span> for<\/span> task<\/span> assignment<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n
[Task #560]<\/span> Update<\/span> mobile<\/span> task<\/span> detail<\/span> screen<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
The PR title is not enough for GitHub linking. The real link should be in the PR body:<\/p>\n\n\n
Related to devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
\n\n\n\n
10. Manual Linking Using GitHub Development Sidebar<\/h1>\n\n\n\n
GitHub also allows manual linking.<\/p>\n\n\n\n
For your case:<\/p>\n\n\n\n
    \n
  1. Open the TaskManager issue.<\/li>\n\n\n\n
  2. Go to:<\/li>\n<\/ol>\n\n\n
    devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n
    1. Find the Development<\/strong> section in the right sidebar.<\/li>\n\n\n\n
    2. Click link\/add item.<\/li>\n\n\n\n
    3. Select the code repository.<\/li>\n\n\n\n
    4. Select the PR or branch.<\/li>\n\n\n\n
    5. Click Apply<\/strong>.<\/li>\n<\/ol>\n\n\n\n
      GitHub\u2019s docs say that from the issue sidebar, you can manually link a PR or branch, and the issue can be in a different repository than the linked PR or branch. (GitHub Docs<\/a>)<\/p>\n\n\n\n
      Important limitation: from the PR sidebar, manual linking is limited to issues in the same repository. From the issue sidebar, cross-repo linking is supported. GitHub\u2019s docs state that PR-sidebar manual linking requires the issue and PR to be in the same repository, while issue-sidebar linking supports a different repository. (GitHub Docs<\/a>)<\/p>\n\n\n\n
      \n\n\n\n
      11. Why You Cannot See All Commit Messages in the TaskManager Issue Timeline<\/h1>\n\n\n\n
      This was your exact problem.<\/p>\n\n\n\n
      You linked the PR\/branch from:<\/p>\n\n\n
      TaskManager<\/span> issue<\/span> #560<\/span> \u2192 Development<\/span> sidebar<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      But you still could not see all commit messages inside the issue timeline.<\/p>\n\n\n\n
      That is normal.<\/p>\n\n\n\n
      Manual Development linking shows that work is connected to the issue. It does not automatically copy every commit message from the PR into the issue timeline. GitHub is more PR-centric than commit-list-centric.<\/p>\n\n\n\n
      So, the best native GitHub flow is:<\/p>\n\n\n
      TaskManager issue\n    \u2193\nLinked PR visible in Development\n    \u2193\nOpen PR\n    \u2193\nGo to Commits tab\n    \u2193\nSee commit messages\n<\/code><\/span><\/pre>\n\n\n
      If you want commit messages directly inside the TaskManager issue, you need automation.<\/p>\n\n\n\n
      \n\n\n\n
      12. Recommended Workflow for Your Team<\/h1>\n\n\n\n
      For each TaskManager issue:<\/p>\n\n\n
      devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 1: Create branch in code repo<\/h2>\n\n\n
      git checkout -b task-560-add-login-validation\n<\/code><\/span><\/pre>\n\n\n
      Step 2: Add commits with issue reference<\/h2>\n\n\n
      git commit -m \"Add login validation for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n
      git commit -m \"Add login validation tests for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n
      git commit -m \"Fix validation error message for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 3: Create PR with proper title<\/h2>\n\n\n
      [Task #560]<\/span> Add<\/span> login<\/span> validation<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 4: Add PR body<\/h2>\n\n\n
      ## Task<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Added login validation\n- Added validation test cases\n- Updated error response\n\n## Testing done<\/span>\n\n- Ran unit tests\n- Tested login flow locally\n\n## Notes<\/span>\n\nThis PR is part of TaskManager issue #560.<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 5: Link PR manually from TaskManager issue<\/h2>\n\n\n\n
      Go to:<\/p>\n\n\n
      TaskManager<\/span> issue<\/span> #560<\/span> \u2192 Development<\/span> \u2192 select<\/span> repo<\/span> \u2192 select<\/span> PR<\/span> \u2192 Apply<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Step 6: Use closing keyword only in final PR<\/h2>\n\n\n
      Closes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      13. Same Issue, Multiple Repositories Example<\/h1>\n\n\n\n
      Assume issue:<\/p>\n\n\n
      devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      You need changes in 3 repos:<\/p>\n\n\n
      frontend-web\nbackend-api\nmobile-app\n<\/code><\/span><\/pre>\n\n\n
      Backend PR<\/h2>\n\n\n
      ## Task<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Added API endpoint\n- Added request validation\n- Added DB migration\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Frontend PR<\/h2>\n\n\n
      ## Task<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Added task form UI\n- Integrated backend API\n- Added error handling\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Mobile PR<\/h2>\n\n\n
      ## Task<\/span>\n\nCloses devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Added mobile task screen\n- Integrated API\n- Completed final<\/span> user flow\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This gives you clean tracking without closing the issue too early.<\/p>\n\n\n\n
      \n\n\n\n
      14. Multiple Issues in One PR<\/h1>\n\n\n\n
      Sometimes one PR completes multiple issues.<\/p>\n\n\n\n
      Same repo example:<\/p>\n\n\n
      Resolves<\/span> #10<\/span>, resolves<\/span> #11<\/span>, resolves<\/span> #12<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      Cross-repo example:<\/p>\n\n\n
      Resolves devops-school-com\/TaskManager#560, resolves devops-school-com\/TaskManager#561<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Mixed example:<\/p>\n\n\n
      Resolves #10, resolves devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      GitHub documents that multiple issues should use full syntax for each issue reference. (GitHub Docs<\/a>)<\/p>\n\n\n\n
      \n\n\n\n
      15. One Issue, Multiple PRs<\/h1>\n\n\n\n
      This is your most common case.<\/p>\n\n\n\n
      Use Related to<\/code> everywhere:<\/p>\n\n\n
      Related to devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Use Closes<\/code> only once, in the final PR:<\/p>\n\n\n
      Closes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      Recommended pattern:<\/p>\n\n\n\n
      Repo<\/th>PR Body<\/th><\/tr><\/thead>
      backend-api<\/td>Related to devops-school-com\/TaskManager#560<\/code><\/td><\/tr>
      frontend-web<\/td>Related to devops-school-com\/TaskManager#560<\/code><\/td><\/tr>
      mobile-app<\/td>Related to devops-school-com\/TaskManager#560<\/code><\/td><\/tr>
      final integration PR<\/td>Closes devops-school-com\/TaskManager#560<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      16. Commit Message Best Practices<\/h1>\n\n\n\n
      16.1 Good Commit Message<\/h2>\n\n\n
      git commit -m \"Add task assignment API for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      16.2 Better Commit Message<\/h2>\n\n\n
      git commit -m \"Add task assignment API\n\nRelated to devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      16.3 Best Multi-Line Commit Message<\/h2>\n\n\n
      git commit -m \"Add task assignment API\n\n- Added task assignment endpoint\n- Added request validation\n- Added service layer method\n- Added unit tests\n\nRelated to devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      16.4 Commit Message for Bug Fix<\/h2>\n\n\n
      git commit -m \"Fix task status filter bug\n\nThe completed task filter was not applying organization scope.\n\nRelated to devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      16.5 Commit Message for Final Fix<\/h2>\n\n\n\n
      Use carefully:<\/p>\n\n\n
      git commit -m \"Fix task assignment workflow\n\nCloses devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      GitHub allows closing keywords in commit messages, but the cleaner workflow is usually to put the closing keyword in the PR body, because PRs are easier to review and audit. GitHub also notes that when a commit message closes an issue, the PR containing that commit will not be listed as the linked PR. (GitHub Docs<\/a>)<\/p>\n\n\n\n
      \n\n\n\n
      17. PR Template for Same-Repo and Cross-Repo Work<\/h1>\n\n\n\n
      Add this file in each code repo:<\/p>\n\n\n
      .github\/pull_request_template.md\n<\/code><\/span><\/pre>\n\n\n
      Template:<\/p>\n\n\n
      ## Task Link\n\n<!-- Same repo example: Related to #123 --><\/span>\n<!-- Cross repo example: Related to devops-school-com\/TaskManager#560 --><\/span>\n\nRelated to devops-school-com\/TaskManager#ISSUE_ID\n\n## What changed?\n\n- \n\n## Testing done\n\n- \n\n## Screenshots \/ Logs\n\n- \n\n## Deployment notes\n\n- \n\n## Final PR?\n\n- [ ] This PR is the final PR for the task\n- [ ] If final, replace `Related to` with `Closes`\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
      For your specific task:<\/p>\n\n\n
      ## Task Link<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- \n\n## Testing done<\/span>\n\n- \n\n## Screenshots \/ Logs<\/span>\n\n- \n\n## Deployment notes<\/span>\n\n- \n\n## Final PR?<\/span>\n\n- [ ] This PR is the final<\/span> PR for<\/span> TaskManager issue #560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      18. Issue Template for TaskManager Repo<\/h1>\n\n\n\n
      In the central TaskManager<\/code> repo, create:<\/p>\n\n\n
      .github\/ISSUE_TEMPLATE\/task.yml\n<\/code><\/span><\/pre>\n\n\n
      Or use a simple Markdown issue template:<\/p>\n\n\n
      ## Task Summary<\/span>\n\nDescribe the task.\n\n## Repositories Involved<\/span>\n\n- [ ] frontend-web\n- [ ] backend-api\n- [ ] mobile-app\n- [ ] other\n\n## Expected PRs<\/span>\n\n- frontend-web:\n- backend-api:\n- mobile-app:\n\n## Acceptance Criteria<\/span>\n\n- [ ] \n- [ ] \n- [ ] \n\n## Linked PRs<\/span>\n\n- \n\n## Final Closure Rule<\/span>\n\nOnly the final<\/span> PR should use<\/span>:\n\nCloses<\/span> devops<\/span>-school<\/span>-com<\/span>\/TaskManager<\/span>#ISSUE_ID<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      For issue #560<\/code>, the issue body can maintain a manual list:<\/p>\n\n\n
      ## Linked PRs<\/span>\n\n- backend-api: devops-school-com\/backend-api#45<\/span>\n- frontend-web: devops-school-com\/frontend-web#88<\/span>\n- mobile-app: devops-school-com\/mobile-app#19<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
      This is very useful because GitHub\u2019s native UI may not give you a perfect central commit list.<\/p>\n\n\n\n
      \n\n\n\n
      19. How to See Work from the TaskManager Issue<\/h1>\n\n\n\n
      Inside TaskManager#560<\/code>, you may see:<\/p>\n\n\n
      Development<\/span>\n-<\/span> backend-api<\/span>#45<\/span>\n-<\/span> frontend-web<\/span>#88<\/span>\n-<\/span> mobile-app<\/span>#19<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      To view commits:<\/p>\n\n\n\n
        \n
      1. Click the linked PR.<\/li>\n\n\n\n
      2. Open the Commits<\/strong> tab.<\/li>\n\n\n\n
      3. Review all commit messages.<\/li>\n\n\n\n
      4. Open Files changed<\/strong> for code review.<\/li>\n\n\n\n
      5. Return to TaskManager issue for final status.<\/li>\n<\/ol>\n\n\n\n
        This is the most natural GitHub-native workflow.<\/p>\n\n\n\n
        \n\n\n\n
        20. If You Want Commit Messages Directly Inside the TaskManager Issue<\/h1>\n\n\n\n
        GitHub does not provide a perfect native \u201cshow all commits from linked PRs inside central issue timeline\u201d view.<\/p>\n\n\n\n
        So use GitHub Actions.<\/p>\n\n\n\n
        The idea:<\/p>\n\n\n
        Developer creates PR in backend-api\n        \u2193\nGitHub Action extracts TaskManager issue ID from PR body\n        \u2193\nAction collects PR commits\n        \u2193\nAction comments on devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        GitHub CLI supports adding comments to issues with gh issue comment<\/code>, including selecting another repository with --repo OWNER\/REPO<\/code>. (GitHub CLI<\/a>)<\/p>\n\n\n\n
        GitHub REST API can also create and manage comments on issues and pull requests. (GitHub Docs<\/a>)<\/p>\n\n\n\n
        \n\n\n\n
        21. GitHub Action Example: Comment Commit Summary on TaskManager Issue<\/h1>\n\n\n\n
        Add this workflow in each code repo:<\/p>\n\n\n
        .github\/workflows\/comment-taskmanager-issue.yml\n<\/code><\/span><\/pre>\n\n
        name: Comment TaskManager Issue with PR Commit Summary\n\non:\n  pull_request:\n    types: [opened, synchronize, reopened, closed]\n\njobs:\n  comment-taskmanager:\n    runs-on: ubuntu-latest\n\n    steps:\n      - name: Extract TaskManager issue ID from PR body\n        id: extract\n        shell: bash\n        run: |\n          PR_BODY=\"${{ github.event.pull_request.body }}\"<\/span>\n          ISSUE_ID=$(echo<\/span> \"$PR_BODY\"<\/span> | grep -oE 'devops-school-com\/TaskManager#[0-9]+'<\/span> | head -1<\/span> | grep -oE '[0-9]+'<\/span>)\n\n          if<\/span> [ -z \"$ISSUE_ID\"<\/span> ]; then\n            echo<\/span> \"No TaskManager issue found in PR body.\"<\/span>\n            echo<\/span> \"found=false\"<\/span> >> \"$GITHUB_OUTPUT\"<\/span>\n            exit<\/span> 0<\/span>\n          fi\n\n          echo<\/span> \"found=true\"<\/span> >> \"$GITHUB_OUTPUT\"<\/span>\n          echo<\/span> \"issue_id=$ISSUE_ID\"<\/span> >> \"$GITHUB_OUTPUT\"<\/span>\n\n      - name: Checkout code\n        if<\/span>: steps.extract.outputs.found == 'true'<\/span>\n        uses: actions\/checkout@v4\n        with:\n          fetch-depth: 0<\/span>\n\n      - name: Build commit summary\n        if<\/span>: steps.extract.outputs.found == 'true'<\/span>\n        id: commits\n        shell: bash\n        run: |\n          PR_NUMBER=\"${{ github.event.pull_request.number }}\"<\/span>\n          PR_TITLE=\"${{ github.event.pull_request.title }}\"<\/span>\n          PR_URL=\"${{ github.event.pull_request.html_url }}\"<\/span>\n          REPO=\"${{ github.repository }}\"<\/span>\n          ISSUE_ID=\"${{ steps.extract.outputs.issue_id }}\"<\/span>\n\n          echo<\/span> \"## Code update from ${REPO}#${PR_NUMBER}\"<\/span> > comment.md\n          echo<\/span> \"\"<\/span> >> comment.md\n          echo<\/span> \"**PR:** ${PR_TITLE}\"<\/span> >> comment.md\n          echo<\/span> \"**PR URL:** ${PR_URL}\"<\/span> >> comment.md\n          echo<\/span> \"**Status:** ${{ github.event.action }}\"<\/span> >> comment.md\n          echo<\/span> \"\"<\/span> >> comment.md\n          echo<\/span> \"### Commits\"<\/span> >> comment.md\n\n          gh pr view \"$PR_NUMBER\"<\/span> \\\n            --repo \"$REPO\"<\/span> \\\n            --json commits \\\n            --jq '.commits[] | \"- `\" + .oid[0:7] + \"` \" + .messageHeadline'<\/span> >> comment.md\n\n      - name: Comment on TaskManager issue\n        if<\/span>: steps.extract.outputs.found == 'true'<\/span>\n        run: |\n          gh issue comment \"${{ steps.extract.outputs.issue_id }}\"<\/span> \\\n            --repo devops-school-com\/TaskManager \\\n            --body-file comment.md\n        env:\n          GH_TOKEN: ${{ secrets.TASKMANAGER_TOKEN }}\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Create a secret in each code repo:<\/p>\n\n\n
        TASKMANAGER_TOKEN\n<\/code><\/span><\/pre>\n\n\n
        That token should have permission to comment on issues in:<\/p>\n\n\n
        devops-school-com\/TaskManager\n<\/code><\/span><\/pre>\n\n\n
        \n\n\n\n
        22. Recommended Final Team Standard<\/h1>\n\n\n\n
        Use this as your official rule.<\/p>\n\n\n\n
        Branch<\/h2>\n\n\n
        task-560-short-description\n<\/code><\/span><\/pre>\n\n\n
        Example:<\/p>\n\n\n
        task-560-add-login-validation\n<\/code><\/span><\/pre>\n\n\n
        Commit Message<\/h2>\n\n\n
        git commit -m \"Add login validation for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        PR Title<\/h2>\n\n\n
        [Task #560]<\/span> Add<\/span> login<\/span> validation<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        PR Body<\/h2>\n\n\n
        ## Task<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- \n\n## Testing done<\/span>\n\n- \n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Final PR Body<\/h2>\n\n\n\n
        Only when the task is fully completed:<\/p>\n\n\n
        Closes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Manual Linking<\/h2>\n\n\n\n
        From the central issue:<\/p>\n\n\n
        TaskManager issue #560 \u2192 Development \u2192 Link PR\/branch<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Optional Automation<\/h2>\n\n\n\n
        Use GitHub Actions to comment PR commit summaries into the TaskManager issue.<\/p>\n\n\n\n
        \n\n\n\n
        23. Common Mistakes and Fixes<\/h1>\n\n\n\n
        Mistake<\/th>Problem<\/th>Correct approach<\/th><\/tr><\/thead>
        Using #560<\/code> in another repo<\/td>Links to issue\/PR #560<\/code> in the current repo, not TaskManager<\/td>Use devops-school-com\/TaskManager#560<\/code><\/td><\/tr>
        Using Closes<\/code> in every PR<\/td>First merged PR may close the central issue too early<\/td>Use Related to<\/code> until final PR<\/td><\/tr>
        Expecting commit messages inside TaskManager issue timeline<\/td>GitHub does not show all linked PR commits directly in central issue timeline<\/td>Open linked PR \u2192 Commits tab, or use GitHub Action<\/td><\/tr>
        Adding issue ID only in branch name<\/td>Branch name alone is not enough for strong tracking<\/td>Add issue reference in PR body and commits<\/td><\/tr>
        Linking PR from PR sidebar for cross-repo issue<\/td>PR sidebar manual linking works for same repo only<\/td>Use TaskManager issue sidebar \u2192 Development<\/td><\/tr>
        Using closing keyword on non-default target branch<\/td>GitHub may ignore the closing keyword<\/td>Target default branch for auto-close<\/td><\/tr>
        Putting issue ID only in PR title<\/td>Title is useful but not enough<\/td>Put full reference in PR body<\/td><\/tr>
        Using commit closing keyword only<\/td>Issue may close, but PR may not appear as linked PR<\/td>Prefer closing keyword in PR body<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n
        24. Complete End-to-End Example for Your Case<\/h1>\n\n\n\n
        Issue:<\/p>\n\n\n
        devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Code repo:<\/p>\n\n\n
        devops-school-com\/backend-api\n<\/code><\/span><\/pre>\n\n\n
        Create branch<\/h2>\n\n\n
        git checkout -b task-560-add-login-validation\n<\/code><\/span><\/pre>\n\n\n
        Make commits<\/h2>\n\n\n
        git add .\ngit commit -m \"Add login validation for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n
        git add .\ngit commit -m \"Add login validation tests for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n
        git add .\ngit commit -m \"Fix validation response format for devops-school-com\/TaskManager#560\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
        Push branch<\/h2>\n\n\n
        git push origin task-560-add-login-validation\n<\/code><\/span><\/pre>\n\n\n
        Create PR<\/h2>\n\n\n\n
        PR title:<\/p>\n\n\n
        [Task #560]<\/span> Add<\/span> login<\/span> validation<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
        PR body:<\/p>\n\n\n
        ## Task<\/span>\n\nRelated to devops-school-com\/TaskManager#560<\/span>\n\n## What changed?<\/span>\n\n- Added login validation\n- Added validation test cases\n- Fixed response format\n\n## Testing done<\/span>\n\n- Ran unit tests\n- Tested login API locally\n\n## Notes<\/span>\n\nThis is part of the central TaskManager issue.\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        If this is final PR<\/h2>\n\n\n\n
        Change:<\/p>\n\n\n
        Related to devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        to:<\/p>\n\n\n
        Closes devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Manual link<\/h2>\n\n\n\n
        Open:<\/p>\n\n\n
        devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        Then:<\/p>\n\n\n
        Development \u2192 Link PR\/branch \u2192 select backend-api PR \u2192 Apply\n<\/code><\/span><\/pre>\n\n\n
        View commits<\/h2>\n\n\n\n
        Inside the TaskManager issue, click the linked PR. Then open the PR\u2019s Commits<\/strong> tab.<\/p>\n\n\n\n
        \n\n\n\n
        25. Final Recommendation<\/h1>\n\n\n\n
        For your setup, the best practical standard is:<\/p>\n\n\n
        Central issues:\ndevops-school-com\/TaskManager\n\nCode changes:\nOther repos\n\nEvery branch:\ntask-ISSUE_ID-short-description\n\nEvery commit:\nMessage + devops-school-com\/TaskManager#ISSUE_ID<\/span>\n\nEvery PR:\n[Task #ISSUE_ID] Title<\/span>\n\nEvery PR body:\nRelated to devops-school-com\/TaskManager#ISSUE_ID<\/span>\n\nOnly final<\/span> PR:\nCloses devops-school-com\/TaskManager#ISSUE_ID<\/span>\n\nFor<\/span> visible commit summaries inside TaskManager:\nUse<\/span> GitHub<\/span> Actions<\/span> automation<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        This gives you the cleanest traceability:<\/p>\n\n\n
        TaskManager issue\n    \u2192 linked PRs\n    \u2192 PR commits\n    \u2192 code changes\n    \u2192 final<\/span> closure\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
        For your specific issue, always use:<\/p>\n\n\n
        devops-school-com\/TaskManager#560<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>","protected":false},"excerpt":{"rendered":"
        1. Introduction In many teams, GitHub Issues, commits, branches, and pull requests are created in the same repository. That is the simple case. But your setup is… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-75882","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75882","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=75882"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75882\/revisions"}],"predecessor-version":[{"id":75883,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75882\/revisions\/75883"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=75882"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=75882"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=75882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
        Important: for cross-repo commenting, use a token that has permission to write comments in devops-school-com\/TaskManager<\/code>. GitHub recommends using minimum required permissions for GITHUB_TOKEN<\/code>, and when a workflow needs permissions not available through GITHUB_TOKEN<\/code>, you can use a GitHub App token or a personal access token stored as a repository secret. (GitHub Docs<\/a>)<\/p>\n\n\n\n
      Also, GitHub says that if closing keywords are used in a commit message, the issue can be closed when that commit is merged into the default branch, but the PR containing that commit will not be listed as a linked PR. (GitHub Docs<\/a>)<\/p>\n\n\n\n
GitHub supports issue references using Username\/Repository#number<\/code> or Organization\/Repository#number<\/code>. (GitHub Docs<\/a>)<\/p>\n\n\n\n
When this PR is merged into the default branch, GitHub will close issue #25<\/code>. GitHub notes that these special keywords are interpreted only when the PR targets the repository\u2019s default branch. (GitHub Docs<\/a>)<\/p>\n\n\n\n