Skip to content

fix:Corrected spelling mistake in the README#9

Merged
0xk4b1r merged 1 commit intoCryptoverseWeb3:mainfrom
ShaikMoAbdullah:fix_README
Jul 8, 2022
Merged

fix:Corrected spelling mistake in the README#9
0xk4b1r merged 1 commit intoCryptoverseWeb3:mainfrom
ShaikMoAbdullah:fix_README

Conversation

@ShaikMoAbdullah
Copy link
Contributor

@ShaikMoAbdullah ShaikMoAbdullah commented Jul 8, 2022

Copy link
Contributor

@0xk4b1r 0xk4b1r left a comment

Choose a reason for hiding this comment

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

That's amazing ✅.

Thanks for the contribution.

@0xk4b1r 0xk4b1r merged commit 52b4914 into CryptoverseWeb3:main Jul 8, 2022
@ShaikMoAbdullah ShaikMoAbdullah deleted the fix_README branch July 8, 2022 17:57
@ShaikMoAbdullah
Copy link
Contributor Author

Thank you.

@ShaikMoAbdullah
Copy link
Contributor Author

Did I follow the right approach? Any feedbacks

@0xk4b1r
Copy link
Contributor

0xk4b1r commented Jul 8, 2022

Did I follow the right approach? Any feedbacks

Yes you did great.

In issues we have to write only about issues
Like there is an issue or a bug.

Example + new tips.

In issues:

  • This is a issue.
  • Screenshot.
  • How to fix.

That's it simple


Just create a PR and mention all the details and tag the issue number
As you did ✅.


If you think PR is not ready 100%, you can create draft PR as well


Optional:
Anyone can see and can fix issues
If you want to work on issues particularly, organization or maintainers can assign you a task

So that in the that time no other will give time on the same issue.

On issue your name will be visible that that is assigned to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README enhancements

2 participants