Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Flutter-cheatsheet.md #233

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Navaneethp007
Copy link

What does this PR do?

Add content(s)

Description

I have added a cheatsheet for flutter

Screenshots or Links

If applicable, add screenshots or a modified UI link to help understand your contribution.

Additional context

Add any other context about your PR.

Checklist:

Follow-up

  • Check the status of GitHub Actions and resolve any reported warnings!

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's great having you contribute to this project

Welcome to the community 🤓

Thanks for joining our community - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

@crescentpartha crescentpartha added hacktoberfest Hacktoberfest Participation hacktoberfest-2022 Hacktoberfest-2022 Participation 📝review-pull-request Reviewing your pull request labels Oct 29, 2022
@Navaneethp007
Copy link
Author

When will the reviewing process start

Copy link
Owner

@crescentpartha crescentpartha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your participation.
Some requirements you need to meet to get a successful PR.

  1. Rename your cheat sheet file from Flutter-cheatsheet.md to flutter-cheatsheet.md
  2. Add your cheatsheet file in README.md file.
  3. Follow the cheatsheet structure like git-cheatsheet.md when you introduce a new cheatsheet.
  4. Try to give a tabular format, if it possible.
  5. Give a table of contents section which contains all the navigation links section-wise.
  6. Keep your cheatsheet simple, readable, and understandable so that developers could review it quickly and find their desired commands, keyboard shortcut, or anything else.
  7. Never use unnecessary commits.
  8. Finally, make sure you read the contributing guidelines before your final submission.

@crescentpartha crescentpartha added modifications-needed Modify the code waiting-for-changes Waiting for require changes labels Oct 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest Hacktoberfest Participation hacktoberfest-2022 Hacktoberfest-2022 Participation modifications-needed Modify the code 📝review-pull-request Reviewing your pull request waiting-for-changes Waiting for require changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants