pyvec / pyvec/naucse.python.cz
Definovat workflow s forky
Open
Nobody has claimed this yet.
discussion
forks
question
- Dominant language
- No language data
- Stars
- 335
- Forks
- 119
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 1
Description
V https://github.com/pyvec/naucse.python.cz/pull/395#issuecomment-383200790 se @frenzymadness ptá:
Merge nebo to nechat běžet z forku?
Jak to chceme dělat?
Až se dohodneme, bylo by dobré to přidat do https://github.com/pyvec/naucse.python.cz/pull/394
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 reading the discussion in the referenced comment on PR 395 and the proposed changes in PR 394. Determine whether contributions should be merged or kept running from forks, then document the agreed workflow in PR 394 and confirm that the contributor path is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100