Update DevOps article to include some examples/links on performing Git operations using the Git Project Tool #6614

[alhambrav]

Ticket reference or full description of what's in the PR

Update DevOps article to include some examples/links on performing Git operations using the Git Project Tool
craftercms/craftercms#6614

[coderabbitai]

Walkthrough

Updated DevContentOps documentation with formatting corrections, Studio Git project workflows, workstation synchronization, content pull-back guidance, an important practices checklist, and a cross-reference anchor.

Changes

DevContentOps documentation

Layer / File(s)	Summary
Repository guide corrections source/by-role/developer/devcontentops.rst	Branching table widths, developer fork text, and section spacing were corrected.
Studio Git project workflows source/by-role/developer/devcontentops.rst	Added Studio sandbox synchronization, Dev/QA/Prod promotion, workstation syncing, content pull-back guidance, important practices, and a blob-storage/content-back anchor.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title matches the main change by describing Git Project Tool examples and links for DevOps documentation.
Description check	✅ Passed	The description follows the required template and includes the PR summary plus the related issue reference.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@source/by-role/developer/devcontentops.rst`:
- Around line 223-229: Clarify in the workflow instructions before the Git pull
steps that the target studio-* branch must first be promoted or synchronized
from the source branch (dev, qa, or prod), or explicitly state that automation
performs this update. Update the corresponding Dev, QA, and Prod instructions so
users do not pull stale studio branches, while preserving the existing Studio
review and publish steps.
- Around line 254-261: Clarify the Content Back workflow in the affected
documentation section: after confirming the merge on dev or qa, document the
required promotion/deployment that updates the corresponding studio-dev or
studio-qa branch, then instruct users to pull that studio-* branch into the
authoring environment via the Git project tool. Update the note to consistently
distinguish server-side promotion from pulling into Studio.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 145f5b64-0ffc-410f-aaa2-82e4dfb33748

📥 Commits

Reviewing files that changed from the base of the PR and between 0568553 and 4a4d186.

📒 Files selected for processing (1)

• source/by-role/developer/devcontentops.rst