Repository navigation
Bring envato-production customisations into master - #37
Merged
Merged
Conversation
Emit an info-level log line with the command before each git invocation in GitRepository#capture_stdout, making it easier to trace slow or failing repository operations in production logs.
When a production deploy includes commits that did not go through a pull request, prefix the Slack warning with <!channel> so the alert is not missed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: Samson is a public repo, do not include Zendesk-internal information, urls, etc.
envato-productioncarries two small code customisations thatmasterlacks: an info-level log line for each git command run byGitRepository#capture_stdout, and a<!channel>prefix on the Slack "commits without a pull request" warning when the stage is production. This PR brings both intomasteras two separate commits so the branches converge.References
Risks
deploy.stage.production?;deployis already in scope in this template so no new nil risk is introduced.