https://github.com/armanriazi/rust-all-in-one-projects

https://github.com/armanriazi/rust-all-in-one-projects

Last synced: 3 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/armanriazi/rust-all-in-one-projects
• Owner: armanriazi
• Created: 2022-12-27T14:08:31.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2023-01-30T12:22:02.000Z (almost 2 years ago)
• Last Synced: 2024-05-02T06:12:36.712Z (6 months ago)
• Language: HTML
• Size: 1.13 MB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml

Awesome Lists containing this project

README

        
## Rust-All-In-One-Projects

### Included All Toturials(Important Sections)

## How to Contribute

Contributions are always welcome! Please use the following guidelines when contributing to `rust-all-in-one-projects`

1. Fork `rust-all-in-one-projects`

2. Clone your fork (`git clone https://github.com/$YOUR_USERNAME/rust-all-in-one-projects && cd rust-all-in-one-projects`)

3. Create new branch (`git checkout -b new-branch`)

4. Make your changes, and commit (`git commit -am "your message"`)

 * I use a [conventional](https://github.com/ajoslin/conventional-changelog/blob/a5505865ff3dd710cf757f50530e73ef0ca641da/conventions/angular.md) changelog format so I can update my changelog using [clog](https://github.com/thoughtram/clog)

 * In addition to the conventions defined above, I also use `imp`, `wip`, `gr`.

 * Format your commit subject line using the following format: `TYPE(COMPONENT): MESSAGE` where `TYPE` is one of the following:

    - `feat` - A new feature

    - `imp` - An improvement to an existing feature

    - `perf` - A performance improvement

    - `tests` - Changes to the testing framework or tests only

    - `fix` - A bug fix

    - `refactor` - Code functionality doesn't change, but underlying structure may

    - `style` - Stylistic changes only, no functionality changes

    - `wip` - A work in progress commit (Should typically be `git rebase`'ed away)

    - `chore` - Catch all or things that have to do with the build system, etc

    - `gr` - Graphics changes

 * The `COMPONENT` is optional, and may be a single file, directory, or logical component. Can be omitted if commit applies globally

5. Run the tests (`cargo test`)

6. `git rebase` into concise commits and remove `--fixup`s (`git rebase -i HEAD~NUM` where `NUM` is number of commits back)

7. Push your changes back to your fork (`git push origin $your-branch`)

8. Create a pull request! (You can also create the pull request first, and we'll merge when ready. This a good way to discuss proposed changes.)