-
Notifications
You must be signed in to change notification settings - Fork 13
Patent and Tech #311
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
base: master
Are you sure you want to change the base?
Patent and Tech #311
Conversation
c4b6510
to
71b9dd3
Compare
@Soumil221 isn't it the same as the one that I had merged patents-and-technologies vaali? |
Again staged and master if you want to run separately you will have to merge stuff separately too |
@heydoyouknowme0 why can't we raise a PR from staged to master, after having the code reviewed that has been merged to staged and is ahead of master. |
Again if you can guarantee the code quality, clean up the tree for staged, manually check for incomplete code for each commit after master, go ahead. The point of this site is long term maintainability and sustainability, not one and done. You can keep updating staged for meeting deadlines in the short term but that doesn't overwrite existing standards. |
I think we can have a small discussion on this.. whenever you have time |
Also, @aryansri-19 and I can maintain master for you, merging and keeping track of the commits that have been merged to staged, just like this commit. So you don't have to worry about this branch and can just focus on deployments. That's until both of the branches achieve feature parity. |
This would be very good😊 |
No description provided.