Skip to content

Add CONTRIBUTING.md with contribution guidelines - #1953

Open
preetk25627-dotcom wants to merge 1 commit into
HSF:mainfrom
preetk25627-dotcom:add-contributing-md
Open

Add CONTRIBUTING.md with contribution guidelines#1953
preetk25627-dotcom wants to merge 1 commit into
HSF:mainfrom
preetk25627-dotcom:add-contributing-md

Conversation

@preetk25627-dotcom

@preetk25627-dotcom preetk25627-dotcom commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

#1951

Summary

This PR adds a CONTRIBUTING.md file that provides guidance for contributors.

Changes

  • Added contribution workflow
  • Added contributor etiquette
  • Added guidance for AI-assisted contributions
  • Linked to the existing website contribution guide

Highlights

  • Welcome new contributors
  • Encourage discussion before significant changes
  • Add guidance for AI-assisted contributions
  • Outline contributor etiquette and pull request expectations
  • Link to the existing website contribution guide

Related to #1951
Screenshot 2026-08-01 at 2 10 43 PM

@netlify

netlify Bot commented Aug 1, 2026

Copy link
Copy Markdown

Deploy Preview for earnest-hotteok-b1e1bf ready!

Name Link
🔨 Latest commit 023842f
🔍 Latest deploy log https://app.netlify.com/projects/earnest-hotteok-b1e1bf/deploys/6a6db12da6b04300080b6f6f
😎 Deploy Preview https://deploy-preview-1953--earnest-hotteok-b1e1bf.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@cantel

cantel commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Thanks, @preetk25627-dotcom . It needs discussion together with the pull request template, so I suspect they will stay open for a couple of weeks as many are away on holiday in August.

@cantel

cantel commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Hello, it's been a long summer break but meetings will start up again soon.

After a few week's break, I think this still reads well. : )

I had 2 comments (my opinions):

  • I still feel like we could avoid a specific emphasis on AI contribution. I think (a) it is quickly going to become outdated (imagining that in the future it is expected that most sw contributions will be with AI-assistance) and (b) it doesn't get to the root of the concern, i.e. that developers should understand/have read the code they're submitting always - whether AI generated or copied from Stack Overflow.
  • I like the idea suggested in Add a statement on usage of AI tools #1919 of adding a part that says "Reviewers may reject PRs if ..." (as in the early draft I suggested in Add a CONTRIBUTING.md file #1951), as it somehow makes it easier to directly close PR spam with just a comment linking to this section of the contributing file .

With that in mind, I'll add 2 edit suggestions - to discuss with others.

Comment thread CONTRIBUTING.md

Contributions of all sizes are welcome, including documentation improvements, typo fixes, bug fixes, and new content. For significant changes or new features, please open an issue first to discuss your proposal before starting work.

## AI-assisted contributions

@cantel cantel Sep 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of a specific emphasis on AI, I suggest replacing this with a more generic section on responsibility

## Act responsibly

Any contribution should be fully understood by you, so, please:
- review and understand all content before submitting it - AI generated or not;
- helpfully disclose the use of AI in your pull request when appropriate;
- verify that the proposed changes are correct and appropriate for the project;
- remain fully responsible for the content of your contribution.

Comment thread CONTRIBUTING.md
- your changes have been reviewed by you;
- your pull request description clearly explains the purpose of the changes;
- your contribution does not introduce unintended modifications.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggest add section

## A PR may immediately be rejected if...

- the PR description provides no motivation for the changes;
- it implements too many changes in one go: In one big PR or a spam flood of many small PRs;
- it appear to be generated solely by AI with little or no human contributor oversight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants