GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - yargs/.github: Yargs organization common files

BranchesTags
Open more actions menu

Latest commit

 

History

2 Commits
2 Commits

Folders and files

NameName
Last commit message
Last commit date
AI_POLICY.md
AI_POLICY.md
 
 
CONTRIBUTING.md
CONTRIBUTING.md
 
 

Repository files navigation

Contributing to Yargs

Me hearties, thanks for your interest in yargs!

Issues

New issues are welcome, whether questions or suggestions or reporting bugs. You are also welcome to contribute by adding helpful comments on an existing issue, and upvoting issues you would like resolved.

We love reproducible code examples in questions and answers.

If you get a satisfactory answer to a question then you can close the issue, but it is ok to leave an issue open for more comments or reactions. Inactive issues may get closed after one month if they have an answer, or after six months otherwise.

Pull Requests

There have been too many low-effort and low-value Pull Requests, so clamping down:

  • Don't open a Pull Request unless invited to do so by a maintainer.
  • Don't open a Pull Request entirely or largely generated by AI, as it would be easier for the maintainer to do it themselves.
  • Unsolicited Pull Requests may be closed without discussion.

Rationale:

  • The human maintainers spend time and effort reviewing every Pull Request that is accepted. Low-effort Pull Requests may be of reasonable quality, but are often low-value, fixing problems that very few users will encounter. They take maintainers away from more valuable work.
  • A low-effort Pull Request is likely to continue with low-effort responses to maintainer interactions, with an AI handling it autonomously or by a human proxy asking the AI. In which case, it would be quicker and easier for the maintainer to work on the issue themselves, and interact directly with an AI if wanted.
  • It is not fun reviewing AI generated Pull Requests.

See also the AI Policy.

About

Yargs organization common files

Contributing

Contributing
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.