├── assets
└── sway.jpeg
├── PULL_REQUEST_TEMPLATE.md
├── .github
└── workflows
│ └── ci.yml
├── CONTRIBUTING.md
└── README.md
/assets/sway.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/refcell/awesome-sway/HEAD/assets/sway.jpeg
--------------------------------------------------------------------------------
/PULL_REQUEST_TEMPLATE.md:
--------------------------------------------------------------------------------
1 | [Please describe your pull request here]
2 |
3 | ## Checklist
4 |
5 | - [ ] The URL is not already present in the list (check with CTRL/CMD+F in the
6 | raw markdown file).
7 | - [ ] Each description starts with an uppercase character and ends with a
8 | period.
Example: `sway - The Sway programming language.`
9 | - [ ] Drop all `A` / `An` prefixes at the start of the description.
10 | - [ ] Avoid using the word `StarkNet` in the description.
11 |
--------------------------------------------------------------------------------
/.github/workflows/ci.yml:
--------------------------------------------------------------------------------
1 | name: CI
2 |
3 | on:
4 | push:
5 | branches: [master]
6 | pull_request:
7 | branches: [master]
8 |
9 | jobs:
10 | ci:
11 | runs-on: ubuntu-latest
12 | steps:
13 | - uses: actions/checkout@v2
14 | - name: Set up Ruby
15 | uses: ruby/setup-ruby@v1
16 | with:
17 | ruby-version: 2.6
18 | - name: Install awesome_bot
19 | run: gem install awesome_bot
20 | - name: Check URLs
21 | run: awesome_bot README.md --allow-redirect --request-delay 0.2
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contribution Guidelines
2 |
3 | Please ensure your pull request adheres to the following guidelines:
4 |
5 | - Search previous suggestions before making a new one, as yours may be a
6 | duplicate.
7 | - Make sure your contribution is useful before submitting.
8 | - Make an individual pull request for each suggestion.
9 | - Use the following format: `[name](link) - Description.`
10 | - Additions should be added in alphabetical order of the relevant category.
11 | - New categories, or improvements to the existing categorization are welcome.
12 | - Keep descriptions short and simple, but descriptive.
13 | - Start the description with a capital and end with a full stop/period.
14 | - Check your spelling and grammar.
15 | - Make sure your text editor is set to remove trailing whitespace.
16 | - The pull request should have a useful title and include a link to the package
17 | and why it should be included.
18 |
19 | ---
20 |
21 | **Working on your first Pull Request?** You can learn how from this free series
22 | [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
23 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |