Escaping job wildcard via backtick does not work
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 176
- Forks
- 65
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 13
Description
I issued the command
@bors try jobs=`dist-various-*`
which did not work:
Unknown value for argument "jobs". Run @bors2 help to see available commands.
That error is not super helpful, I know about the command, I just don't know how to escape *... and the help text does not indicate that it seems.
I expected this to work similar to "try-job: dist-various-*" in the PR description. The docs even say
When using glob patterns, you might want to wrap them in backticks (`) to avoid GitHub rendering the pattern as Markdown.
but that does only seem to apply to jobs defined in the PR description (whereas the docs make it sound like it also should work for the jobs command parameter).
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
Start by reproducing the @bors try command with jobs=dist-various-*, then trace the jobs argument parsing and the help text for wildcard handling. Compare this behavior with try-job patterns in PR descriptions and the linked CI documentation; done means the command accepts the escaped wildcard or clearly documents the supported syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100