Allow to choose the backend behind the security check prerequisite
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 459
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
FEATURE: This is a follow up of https://github.com/liip/RMT/pull/163#issuecomment-775958033
It would be nice to be able to choose https://github.com/enlightn/security-checker instead of fabpot/local-php-security-checker
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
The issue concerns RMT's release workflow and names fabpot/local-php-security-checker and enlightn/security-checker as alternative backends. Start by tracing where the security-check prerequisite is configured or invoked; done means a user can choose either backend for that prerequisite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100