Development guide should suggest including links to original workflow files

Open Beginner friendly
#207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
ci-cd, documentation

Research direction

Start with docs/development.md and review the linting and content-checking workflows run against each pull request. Identify the upstream workflow sources for comparison and add links where appropriate. Done means the development guide, and any updated workflows, link to their original upstream files.

Written by the indexing model from the issue text.

Description

enhancement good first issue infrastructure

For reference/comparison purposes, all of our workflows should provide a link to the workflows they're based on in the respective upstream repositories. The best place to make this change is in the docs/development.md file, but a change to the various linting/content checking workflows run against each PR would be good too.

Dominant language
Python
Stars
0
Forks
0
Avg merge
17h 2m
Merged PRs (30d)
959

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from riseproject-dev/python-wheels

All issues in riseproject-dev/python-wheels

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.