Repository navigation
docs: clarify deployment queues and managed pointer hashes - #640
efraespada merged 3 commits into
Conversation
…cope: clarify deployment queues and managed pointer hashes
|
To preview the documentation for this pull request, visit the following URL:
|
Bugbot: review complete
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #640 +/- ##
===========================================
+ Coverage 90.94% 94.10% +3.16%
===========================================
Files 135 950 +815
Lines 6251 30548 +24297
Branches 1338 8965 +7627
===========================================
+ Hits 5685 28748 +23063
- Misses 172 704 +532
- Partials 394 1096 +702 🚀 New features to boost your workflow:
|
Copilot approval · Waiting for evidenceStatus: Waiting for a complete Bugbot review of this head. Technical evidenceRevision: |
|
/copilot sync-branch --no-agent |
…ed-agents-md-hash-scope
Branch synchronized
6 verification checks passed. |
|
/copilot sync-branch |
…ed-agents-md-hash-scope
Branch synchronized
The fixer resolved 1 conflicted file. 6 verification checks passed. |
Clarifies that GitHub Actions supports
queue: maxfor deployment concurrency and documents how to verify the managedAGENTS.mdpointer hash. These explanations help prevent valid deployment settings or correct manifest hashes from being mistaken for errors.What changed
queue: max, its 100-item limit, and itscancel-in-progressconstraint, with links to GitHub documentation.AGENTS.mdpointer hash covers only the marker-bounded block, normalizes CRLF to LF, and excludes surrounding text and the trailing newline.Validation
Closes #637