pipe-cd / pipe-cd/docs-mcp-server
Add automated release flow
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 4
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 2
Description
What you want?:
The current flow:
- Update versions in package.json and src/main.ts
- Open a PR
- Review and merge the PR
- Create a Release with a new Tag
- Trigger the release-package action to release the npm package
I want to merge:
- [1],[2]
- [4],[5]
Why is it needed? / Without it, what's the problem?:
toil
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review package.json and src/main.ts to understand the version updates, then inspect the existing release-package action and repository release process. Done means the requested versioning, pull request, release/tag, and npm package steps are combined into an automated flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100