We invite you to contribute to Flutter Icons! Please read the following sections
One of the most useful tasks, closely related to triage, is finding and filing bug reports. Testing beta releases, looking for regressions, creating test cases, adding to our test suites, and other work along these lines can really drive the quality of the product up. Creating tests that increase our test coverage, writing tests for issues others have filed, all these tasks are really valuable contributions to open source projects.
If you would prefer to create some cool design for extensions that i might forgot, don't hesitate to fork the repo and submit a pull request, it will be checked by Antoine and if it correspond to the norm you're icon will appear in the next version of the vscode extension.
- Do not push directly to the main branch.
- Create a branch related to the current issue and make a pull request (PR) to merge the branch.
- At least one person must approve the PR before it can be merged.
To develop for Flutter icon, you will eventually need to become familiar with our processes and conventions. This section lists the documents that describe these methodologies. The following list is ordered: you are strongly recommended to go through these documents in the order presented.
the name of the branch must be the number of the issue followed by the name of the issue with a gitmoji that explian expilicitly the change.
Here's an example of a valid PR message: 🔀 Add [ICON_NAME]
- 🌐 = Docker & Virtual Env
- ❇️ = to new features in the workspace
- 🧪 = test politics
- 🙈 = add ignore file
- 🎨 = improve some functions
- 🐛 = fix some bugs
- 📝 = update documentation
- 🚧 = start to build new feature
- ➖ = remove code or file/folder
- 🧱 = split functions
- 🩹 = norm code