diff --git a/.github/workflows/contributor-twitter.yml b/.github/workflows/contributor-twitter.yml deleted file mode 100644 index 62a3a95057eeb7..00000000000000 --- a/.github/workflows/contributor-twitter.yml +++ /dev/null @@ -1,21 +0,0 @@ -name: contributor-twitter -on: - issues: - types: [labeled] -jobs: - tweet: - runs-on: ubuntu-latest - steps: - # This has essentially zero costs and helps debugging if the workflow fails. - - uses: hmarr/debug-action@master - - uses: ethomson/send-tweet-action@v1 - if: ${{ github.event.label.name == 'good first issue' && github.event.issue.state == 'open' }} - with: - status: > - A new issue in the @materialui repository has been labelled as a good first issue. If you haven't contributed before, now's your chance! - (Just check that it hasn't already been assigned to anyone before starting.) - ${{ github.event.issue.html_url }}" - consumer-key: ${{ secrets.TWITTER_CONSUMER_API_KEY }} - consumer-secret: ${{ secrets.TWITTER_CONSUMER_API_SECRET }} - access-token: ${{ secrets.TWITTER_ACCESS_TOKEN }} - access-token-secret: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }} diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 85eed44953d7f3..5dba986880de04 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -18,7 +18,6 @@ Working on your first Pull Request? You can learn how from this free video serie [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github) To help you get your feet wet and get you familiar with our contribution process, we have a list of [good first issues](https://github.com/mui-org/material-ui/issues?q=is:open+is:issue+label:"good+first+issue") that contain changes that have a relatively limited scope. This label means that there is already a working solution to the issue in the discussion section. Therefore, it is a great place to get started. -If you didn't find a suitable issue you can also follow [@MuiContrib](https://twitter.com/MuiContrib) which automatically tweets new good first issues. We also have a list of [good to take issues](https://github.com/mui-org/material-ui/issues?q=is:open+is:issue+label:"good+to+take"). This label is set when there has been already some discussion about the solution and it is clear in which direction to go. These issues are good for developers that want to reduce the chance of going down a rabbit hole.