Checked for duplicates
Have you checked for duplicate issue tickets?
- Yes - I've already checked
Describe the bug
A clear and concise description of what the bug is. Plain-text snippets preferred but screenshots welcome.
The scan fails to find things like CONTRIBUTING.md for certain repositories, even when they appear in a GitHub organization's .github repository.
What did you expect?
A clear and concise description of what you expect to happen
I expected at least a yellow or partial pass for the presence of a centralized CONTRIBUTING.md within a .github folder in an organization. I don't think a full green pass should be given due to the fact that not having a CONTRIBUTING.md inside a README but rather on a .github repository means that the code is less portable outside of GitHub.
Reproducible steps
How would we reproduce this bug? Please walk us through it step by step. Plain-text snippets preferred but screenshots welcome.
- Use the SLIM leaderboard to scan for https://github.com/NASA-PDS/validate
- Notice it gives a failure for the CONTRIBUTING.md check
- Notice the repository still points to a valid, centralized CONTRIBUTING.md when a new issue ticket is created (under the main text box block)
What is your environment?
Include any computer hardware, operating system, framework, browser, time-of-day or other contextual information related to your issue
N/A
Checked for duplicates
Describe the bug
The scan fails to find things like CONTRIBUTING.md for certain repositories, even when they appear in a GitHub organization's
.githubrepository.What did you expect?
I expected at least a yellow or partial pass for the presence of a centralized CONTRIBUTING.md within a
.githubfolder in an organization. I don't think a full green pass should be given due to the fact that not having a CONTRIBUTING.md inside a README but rather on a .github repository means that the code is less portable outside of GitHub.Reproducible steps
What is your environment?
N/A