-
-
Notifications
You must be signed in to change notification settings - Fork 255
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
In case of Merge Conflicts #126
Comments
I guess it won't work if you end up sending a pr but another pr was merged after you send a pr then the conflicts will persist. |
Yes, but it is important to update the project_doc , so the contributors should raise the PR again after fetching upstream @Manas1820 |
None is fetching their Repo which is causing the problems with Pull Requests |
In case of conflicts in the Readme for contributors list @ron2111 can add this - https://github.com/marketplace/actions/auto-add-contributors |
that's great, @ron2111 we can use this to make readme file task easier |
I have used it and seen it used many times and the UI generated is cool too |
Before making any Pull Request always fetch your repo to the latest and after that send the Pull Request to avoid any conflicts.
Do not edit the Readme file.
Add your project info in project_doc.md after fetching the GitHub Repo
The text was updated successfully, but these errors were encountered: