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

chore(null): add yarn null:progress #3033

Merged
merged 1 commit into from
Jul 7, 2020

Conversation

dbjorge
Copy link
Contributor

@dbjorge dbjorge commented Jul 6, 2020

Description of changes

This implements a new script that generates a progress message for use with our standup dashboard. yarn null:progress emits stdout like this:

## Web strict-null progress

**29%** complete (**387**/1328 non-test files)

*Contribute at [#2869](https://github.com/microsoft/accessibility-insights-web/issues/2869). Last update: Mon Jul 06 2020*

...which renders in the dashboard widget like this:

screenshot of above output as-rendered in dashboard

Pull request checklist

  • Addresses an existing issue: Codebase should use strict null checks #2869
  • Ran yarn fastpass
  • [n/a] Added/updated relevant unit test(s) (and ran yarn test)
  • [n/a] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
  • PR title AND final merge commit title both start with a semantic tag (fix:, chore:, feat(feature-name):, refactor:). See CONTRIBUTING.md.
  • [n/a] (UI changes only) Added screenshots/GIFs to description above
  • [n/a] (UI changes only) Verified usability with NVDA/JAWS

@dbjorge dbjorge requested a review from a team as a code owner July 6, 2020 23:58
@dbjorge dbjorge closed this Jul 7, 2020
@dbjorge dbjorge reopened this Jul 7, 2020
@dbjorge dbjorge merged commit a05e8b3 into microsoft:master Jul 7, 2020
@dbjorge dbjorge deleted the null-progresss branch July 7, 2020 00:40
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.

2 participants