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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added examples for squashing #5368

Closed
wants to merge 1 commit into from
Closed

Conversation

OskarStark
Copy link
Contributor

No description provided.

@javiereguiluz
Copy link
Member

@OskarStark thanks for adding this tip about squashing commits.

However, I'd like to propose to not merge this PR and even to remove any reference to commit squashing. Why? Because Symfony project uses a proprietary tool which automatically squashes all commits before merging. That's why on symfony and symfony-doc we no longer ask users to squash their commits.

The less hurdles we define for collaborating with Symfony, the better.

@OskarStark
Copy link
Contributor Author

Hey @javiereguiluz

thanks for the detailed answer. I agree with you , but then I would write down explicitly so.

@hurdeless: 👍

@javiereguiluz
Copy link
Member

@OskarStark if the Symfony doc managers agree on removing any reference to squashing commits, I agree with you about explaining that we no longer require squashing. Thanks.

@OskarStark
Copy link
Contributor Author

👍 lets see, what they say! 😃

@xabbuh
Copy link
Member

xabbuh commented Jun 9, 2015

For me, that's okay. But I leave the final word to @weaverryan and @wouterj who do the actual merges.

@weaverryan
Copy link
Member

+1 - let's remove everything about squashing. Thanks @OskarStark for bringing attention on this - let's make things easier!

@xabbuh
Copy link
Member

xabbuh commented Jun 22, 2015

@OskarStark Can you please remove all the squashing stuff then? :)

@OskarStark
Copy link
Contributor Author

New PR here: #5432

@xabbuh
Copy link
Member

xabbuh commented Jun 24, 2015

closing in favor of #5432 then

@xabbuh xabbuh closed this Jun 24, 2015
@wouterj
Copy link
Member

wouterj commented Jun 26, 2015

Thank you for your patience and great actions on this PR Oskar. You deserve the Documenation Contributor Badge on SensioLabs Connect (which will be awared in a few hours/days)! :)

wouterj added a commit that referenced this pull request Jun 26, 2015
This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes #5368).

Discussion
----------

added examples for squashing

Commits
-------

7d279e3 added examples for squashing
@wouterj
Copy link
Member

wouterj commented Jun 26, 2015

Hmm, our merge tool didn't really get which PR I wanted to merge...

@OskarStark
Copy link
Contributor Author

yeah, great, thank you!

@problem: can i help @wouterj

wouterj added a commit that referenced this pull request Jun 26, 2015
This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes #5432).

Discussion
----------

removed squashing stuff. fixes #5368

added explanation, why it is no longer necessary

Commits
-------

e446316 removed squashing stuff
@wouterj
Copy link
Member

wouterj commented Jun 26, 2015

I believe I've merged the correct PR now (and I've reverted this merge)

@OskarStark
Copy link
Contributor Author

@wouterj didn't get the badge already :(

@xabbuh
Copy link
Member

xabbuh commented Jun 28, 2015

@OskarStark Is the e-mail address you used in the commit also associated with your SensioLabs Connect account?

@OskarStark
Copy link
Contributor Author

yes it is

@OskarStark
Copy link
Contributor Author

maybe it is, because @wouterj merged the other PR?

@wouterj
Copy link
Member

wouterj commented Jun 28, 2015

@OskarStark sensiolabs connect uses the commits, and you are the author of some commits in the doc repository: https://github.com/symfony/symfony-docs/commits?author=OskarStark

There has to be something wrong with your emailadress. On the doc contributors page, you're on place 622 at the moment of writing this comment. As you can see, it displays just your name and no link to your sensiolabs account. This means it can't match your commits to your sensiolabs profile.

@javiereguiluz
Copy link
Member

@OskarStark this issue happens when the GitHub email is not exactly the same as the SensioLabs Connect profile one. The solution is very easy: you can add any number of emails in your SensioLabs Connect account at https://connect.sensiolabs.com/#!email

However, you say that the email address is the same ... so I'm going to investigate which could be the cause of this problem.

@OskarStark
Copy link
Contributor Author

could this be the problem?

Keep my email address private
We will use OskarStark@users.noreply.github.com when performing web-based Git operations and sending email on your behalf. If you want command line Git operations to use your private email you must

this is from the github settings page

@wouterj
Copy link
Member

wouterj commented Jun 28, 2015

@OskarStark I think that could be the problem. The solution is to add this email to the email list on your SensioLabs account.

As you can see, the Github API indeed returns your commits with the OskarStark@users.noreply.github.com email adress: https://api.github.com/repos/symfony/symfony-docs/pulls/5368/commits

@OskarStark
Copy link
Contributor Author

and for this pr is used the web interface completely

@OskarStark
Copy link
Contributor Author

@wouterj i will do, give me a second

@wouterj
Copy link
Member

wouterj commented Jun 28, 2015

(be aware that after you added your email, you have to wait until the system rebuilds, so check again tomorrow if everything is fixed)

@OskarStark
Copy link
Contributor Author

ok, i added it, but i'm not sure if i get a confirmation mail to this mailadress

@javiereguiluz
Copy link
Member

Sadly the badges aren't granted in a retroactive fashion when changing or updating the emails, so we'll need to wait until the next contribution.

@OskarStark OskarStark deleted the patch-2 branch June 17, 2019 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants