Create tests for old version of Heroku CLI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
Research direction
Start by reading PR #383 to understand the Heroku CLI change and the old behavior it replaces. Install the old CLI from the source at https://github.com/heroku/cli, then locate the relevant test entry points in Dallinger. Done means tests cover both the old and new CLI behavior.
Written by the indexing model from the issue text.
Description
PR #383 handles a change in the Heroku CLI. It would be useful to have tests that target both the old and new behavior. Old version of the CLI can be installed from source, which is available at: https://github.com/heroku/cli.
- Dominant language
- Python
- Stars
- 123
- Forks
- 44
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 6
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.
More from Dallinger/Dallinger
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
PsyNet
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 48/100
-
PsyNet
All issues in Dallinger/Dallinger
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100