-
Notifications
You must be signed in to change notification settings - Fork 0
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
Phing Email Key in .websharks.json
#117
Comments
Set `user.email` in lite repo clone. See: #117
Next Release Changelog:
|
@raamdev Here's the data you need in "phings": {
"github": {
"username": "",
"email": "",
"api_key": ""
},
"aws": {
"access_key": "",
"secret_key": "",
"salt": ""
},
"slack": {
"username": "",
"email": "",
"api_webhook_url": ""
}
} Note: You can leave the Slack webhook URL empty for now. I'll post details about how to add this in the issue related to Slack notifications later. UPDATE: See: #108 (comment) |
@raamdev writes...
My default email address in my global git config is
xxxx@xxxxxxxx.com
, as I have lots of other personal projects. In my WebSharks repos, I set my email address toxxxx@xxxxxxxxxxx
so that's what shows up in my commits for those repos, however since Phing is cloning new repos and working from those, my global default email address gets used when Phing makes commits.Propose that we read from
.websharks.json
when the repo is cloned:The text was updated successfully, but these errors were encountered: