Contribution guidelines/maintainers: flow for editing/adding new files

Open
#78 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

No files, tests, or entry points are named, and the body only quotes a discussion about editing or adding files in pull requests. First clarify the intended contributor and maintainer flow with the project; then identify the contribution-guideline material to update and agree on the documentation's completed scope.

Written by the indexing model from the issue text.

Description

<ISSOtm> Right, yes, you can't do that for files that haven't been edited. But, since you have upstream push access, you can push directly to the PR branch!
<ISSOtm> As long as you keep it as separated commits, then those can be reverted separately; it's also possible to restrict the changes being reviewed in the Files tab to specific commit (ranges), so it should be okay

Dominant language
Assembly
Stars
34
Forks
16
PR merge metrics
No merged PRs in 30d

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 gbdev/gbdev.github.io

All issues in gbdev/gbdev.github.io

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.