From de00a620630e8192ecafbc57cac1ebc64e2470fd Mon Sep 17 00:00:00 2001 From: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Date: Thu, 7 Mar 2024 09:35:57 -0500 Subject: [PATCH] Update contributing --- .github/CODE_OF_CONDUCT.md | 10 ---------- .github/CONTRIBUTING.md | 13 ++++++++----- 2 files changed, 8 insertions(+), 15 deletions(-) delete mode 100644 .github/CODE_OF_CONDUCT.md diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md deleted file mode 100644 index 7ce9543c5173..000000000000 --- a/.github/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,10 +0,0 @@ -# Tailwind CSS Community Guidelines - -The following community guidelines are based on [The Ruby Community Conduct Guidelines](https://www.ruby-lang.org/en/conduct/). - -This document provides community guidelines for a respectful, productive, and collaborative place for any person who is willing to contribute to the Tailwind CSS project. It applies to all “collaborative space”, which is defined as community communications channels (such as mailing lists, submitted patches, commit comments, etc.). - -- Participants will be tolerant of opposing views. -- Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks. -- When interpreting the words and actions of others, participants should always assume good intentions. -- Behaviour which can be reasonably considered harassment will not be tolerated. diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 597de4a027c5..f1722bf4fab5 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,12 +1,16 @@ # Contributing -Thanks for your interest in contributing to Tailwind CSS! Please take a moment to review this document **before submitting a pull request**. +## Bug fixes -## Pull requests +If you've found a bug in Tailwind that you'd like to fix, [submit a pull request](https://github.com/tailwindlabs/tailwindcss/pulls) with your changes. Include a helpful description of the problem and how your changes address it, and provide tests so we can verify the fix works as expected. -**Please ask first before starting work on any significant new features.** +## New features -It's never a fun experience to have your pull request declined after investing a lot of time and effort into a new feature. To avoid this from happening, we request that contributors create [a feature request](https://github.com/tailwindlabs/tailwindcss/discussions/new?category=ideas) to first discuss any significant new ideas. This includes things like adding new utilities, creating new at-rules, etc. +If there's a new feature you'd like to see added to Tailwind, [share your idea with us](https://github.com/tailwindlabs/tailwindcss/discussions/new?category=ideas) in our discussion forum to get it on our radar as something to consider for a future release. + +**Please note that we don't often accept pull requests for new features.** Adding a new feature to Tailwind requires us to think through the entire problem ourselves to make sure we agree with the proposed API, which means the feature needs to be high on our own priority list for us to be able to give it the attention it needs. + +If you open a pull request for a new feature, we're likely to close it not because it's a bad idea, but because we aren't ready to prioritize the feature and don't want the PR to sit open for months or even years. ## Coding standards @@ -31,4 +35,3 @@ npm run build && npm test ``` Please ensure that the tests are passing when submitting a pull request. If you're adding new features to Tailwind, please include tests. -