Skip to content

chore: setup git before publishing the builds #2197

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

Merged
merged 1 commit into from
Dec 13, 2016

Conversation

devversion
Copy link
Member

@devversion devversion commented Dec 13, 2016

  • It looks like Git is unable to push the changes right now, because they don't have any committer name & email set

Fixes the following issue: https://travis-ci.org/angular/material2/jobs/183455202#L331

@jelbourn It takes more time to get it working, because everything works locally, but on Travis the environment is different and sometimes does not work properly.

* It looks like Git is unable to push the changes right now, because they don't have any commiter name & email set
@devversion devversion requested a review from jelbourn December 13, 2016 16:05
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 13, 2016
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Dec 13, 2016
@jelbourn jelbourn merged commit 656ef22 into angular:master Dec 13, 2016
@devversion devversion deleted the chore/per-commit-git-config branch December 13, 2016 17:41
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants