-
Notifications
You must be signed in to change notification settings - Fork 71
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 Pull Request Template #75
Comments
@gauthamzz what do you think about this template? |
That's contribution guides we already have that . Just link that it's enough. |
Should I create a link for this template in the readme.md file. |
No. See this https://github.com/fossiiita/opencode2017/blob/master/PULL_REQUEST_TEMPLATE.md don't add the last part. And tell them to read the docs once. |
You mean I can add this one. From code practices to tutorials. Am I right? |
The link I send is what we want. It's pull request template it shouldn't be huge. And remove that part of link . Instead make like add relevant images in the comment |
* added issues open badge * added issues open badge * added issues open badge * Added zulip chat and Coday badge * Modified issues open badge for showing current opened issues * Added Download from Chrome-Webstore badge * modified chrome webstore badge * Update README.md * updating * updating * updating * Adding PullRequestTemplate.md * Adding PullRequestTemplate.md * Created a pull request template * Created a pull request template * Modifying pull request template * Added Contributing.md and PullRequestTemplate.md files
@gauthamzz Can we set up a slack channel for Anna. I know that we have zulip-chat. But I think slack would be more attractive and user-friendly. I just want your opinion. |
we promote opensource thats why we use zulip. |
Ok. I was saying because I haven't used Zulip. But no problem. I am adaptable to change. hahaha. |
I have used slack and discord as well. I think of them two discord is better. But for zulip is the best for our purpose |
Should check for:-
The text was updated successfully, but these errors were encountered: