zaproxy / zaproxy/actions-common
Road ahead
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 18
- Avg merge
- 4h 12m
- Merged PRs (30d)
- 5
Description
Hi! After the first PR, I would like to talk a bit about the road ahead before taking this on. On the meta level I would like to understand what I can do to get PRs merged faster, and, on a content level, align on a roadmap.
For the roadmap, I currently see these steps:
- Automatically publish new versions of this package to npm (this requires hands-on support as I don't have the key to publish to npm and therefore can't set this up alone)
- Update the actions to the new version, or even add something that automatically updates them when this package changes
- Add the ideas from #44 and related tests.
I'm happy about feedback on the roadmap, but would also love to understand what I can do to speed up the merge process and discussion. I could e.g. offer to have a synchronous 30 minute session when a PR is done with everyone who is needed to approve the PR to discuss what needs to be done. But I'm also open to other suggestions.
What do you think?
Contributor guide
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
Read this issue alongside #44 and its related tests first. Confirm with maintainers which publishing, action-update, and follow-up work is in scope; done is an agreed roadmap and a separately actionable plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, developer-experience, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100