StackExchange / StackExchange/Stacks
Wrap publishing into a single command
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 672
- Forks
- 107
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 26
Description
There are quite a few steps for publishing a new version of Stacks. We ought to consider wrapping those into a custom script that runs the proper commands for us.
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
No files, tests, or entry points are named. Start by inspecting the repository's existing scripts and the current manual publishing steps; done means one custom command reliably runs the required publishing sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100