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

Reduce output from the sync down step #32933

Merged
merged 3 commits into from Jan 30, 2020
Merged

Conversation

bethanyaconnor
Copy link
Contributor

These messages are exceeding Slack's rate limits and therefore could hide real errors or warnings. We rarely sync down for specific languages so I don't think there's a benefit in seeing what languages have been downloaded.

Screenshot 2020-01-30 at 1 59 38 PM

Links

Testing story

Reviewer Checklist:

  • Tests provide adequate coverage
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

@bethanyaconnor bethanyaconnor requested a review from a team as a code owner January 30, 2020 22:00
bin/i18n/sync-down.rb Outdated Show resolved Hide resolved
Co-Authored-By: Elijah Hamovitz <elijahhamovitz@gmail.com>
@bethanyaconnor bethanyaconnor merged commit a4f756e into staging Jan 30, 2020
@bethanyaconnor bethanyaconnor deleted the quiet-i18n-pipeline branch January 30, 2020 23:55
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

Successfully merging this pull request may close these issues.

None yet

2 participants