PowerShell / PowerShell/Win32-OpenSSH
Document how CI works
Open
Nobody has claimed this yet.
Area-Build
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Appveyor is reporting that my PR is not good: https://ci.appveyor.com/project/PowerShell/openssh-portable
It's unclear to me how the CI even works, the Appveyor artifacts don't seem to be in the default branch. So it's hard to figure out how to fix it.
cc @bingbing8
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 linked Appveyor project and compare its artifacts with the default branch. Trace how CI runs for pull requests and where its artifacts go, then document that workflow and how contributors should diagnose failures. Done means a newcomer can understand the CI process and determine how to fix a failing build.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100