This repository was archived by the owner on Mar 23, 2026. It is now read-only.
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the AppLoggers delivery/tagging workflow documentation to explicitly separate “merge to main” from “create/push a release tag”, and adds guidance for interpreting user intent so docs/workflow-only changes can merge without triggering a release.
Changes:
- Add a new “Tag Decision Matrix” reference document defining tag-eligible vs non-tag-eligible scenarios.
- Update the documented release sequence to include an explicit tag-eligibility decision point (with a docs-only example).
- Update skills/agent guidance to treat merge-to-main and release tagging as separate decisions and discourage auto-tagging.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/skills/applogger-release-tagging/references/tag-decision-matrix.md | Adds a decision matrix for tag eligibility. |
| .github/skills/applogger-release-tagging/references/release-sequence.md | Inserts an explicit “decide tag-eligibility” step and a docs-only no-tag example. |
| .github/skills/applogger-release-tagging/SKILL.md | Adds tag-eligibility rules and intent interpretation; links new matrix reference. |
| .github/skills/applogger-change-delivery/SKILL.md | Adds guidance to avoid assuming every merge should be tagged; adds eligibility checkpoint. |
| .github/agents/applogger-delivery-engineer.agent.md | Updates agent hard rules and workflow steps to avoid automatic tagging after merges. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
59
to
61
| 2. Run [release verification](./references/release-verification.md). | ||
| 3. If release config changed, verify package permissions and version propagation. | ||
| 4. Confirm the GitHub Release and package publication completed. |
| 6. Push the integrated change to `dev`. | ||
| 7. Open PR from `dev` to `main`. | ||
| 8. Merge only after checks are green. | ||
| 9. Decide whether the merged change is release-tag eligible before invoking the release flow. |
Comment on lines
+23
to
+27
| 1. complete docs change | ||
| 2. push to `dev` | ||
| 3. open PR `dev -> main` | ||
| 4. merge after green checks | ||
| 5. stop there, no tag |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation