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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

development based on PRs even from core devs #20

Closed
cordoval opened this issue May 29, 2014 · 9 comments
Closed

development based on PRs even from core devs #20

cordoval opened this issue May 29, 2014 · 9 comments

Comments

@cordoval
Copy link

can we propose so that everybody sends PRs, even core devs, so that we can comment and see better diffs, skimming over commits is not good even though github aggregates the stuff. Please. 馃懚 thanks!

@harikt
Copy link
Member

harikt commented May 29, 2014

@cordoval not sure this works.

@pmjones is the only person who pushes to core. It is small typo / changes I do talk, and we haven't moved to a long conversations on it.

As github allows it nicely I feel let this be an exception for Paul ;) .

@cordoval
Copy link
Author

trust me, it does, and no exceptions, only for tags or reverts that could hold, same as in Symfony and elsewhere I have seen.

@harikt
Copy link
Member

harikt commented May 29, 2014

I will wait to hear what @pmjones thinks about the idea. And sometimes you are right when there are more commits on a day hard to follow the changes.

@harikt
Copy link
Member

harikt commented May 30, 2014

I wonder whether we can search the comments inside PR. ( comments made by other developer in between the code in the review process )

@cordoval
Copy link
Author

of course and they hide when they are addressed, we just did that on the PR you reviewed for me.

@cordoval
Copy link
Author

review process does not happen on code you write in between, review process happens on the total diff those commits amount, in rare cases you can reference those. but launching a thread in a commit commented is not good imo, if there is a request it can easily get lost.

@pmjones
Copy link
Member

pmjones commented Jun 9, 2014

@cordoval at first i thought the team was too small to really support this, but on thinking about it, i don't see any real problem here. i'll start making my own pmjones forks of the branches and begin working from there. it's a good idea; thanks.

@harikt
Copy link
Member

harikt commented Jun 9, 2014

馃憤 great Paul.

@pmjones
Copy link
Member

pmjones commented Jun 10, 2014

I have forked all the repos; further commits will come as pull requests.

@pmjones pmjones closed this as completed Jun 10, 2014
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

No branches or pull requests

3 participants