chore: rename reusable workflow analyze.yml -> publish.yaml#4
Merged
Conversation
The reusable-workflow path is part of the public API once tagged. This renames before the v1 tag so the install snippet reads as 'znat/gitpulse/.github/workflows/publish.yaml@v1' and the workflow's own name becomes 'Gitpulse Publish' to better describe what it does end-to-end (analyze + build + publish to Pages). - .github/workflows/analyze.yml -> publish.yaml - self-deploy.yml updated to call the new path - README install snippet updated
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Rename the reusable workflow file before tagging `v1`, so the install snippet reads as the (slightly) shorter, more descriptive:
```yaml
uses: znat/gitpulse/.github/workflows/publish.yaml@v1
```
instead of the prior `analyze.yml` name. "Publish" better describes what the workflow does end-to-end (analyze + build + deploy to Pages); "analyze" was only the first step.
The reusable-workflow file path is part of the public API once tagged, so this is the right moment — before any consumer can pin to it.
Changes
Note on file extension
The file is `.yaml` (matching what was requested) where the rest of the repo uses `.yml`. GitHub Actions accepts both. Happy to flip to `.yml` for repo-wide consistency if preferred — say the word.
Test plan