cloudfoundry / cloudfoundry/stratos
Migrate non-jetstream requests to use the new api pipline
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
The github and gitlab requests are still using their own effect. Look at the github single commit action builders and follow that pattern to see how to make non-jetstream requests using the api pipeline.
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
Start with the GitHub single commit action builders mentioned in the issue and trace their API pipeline usage. Compare the GitHub and GitLab request effects with that pattern, then verify that both sets of non-Jetstream requests use the API pipeline consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab, typescript
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100