Follow new updates and improvements to PureType.
August 21st 2024
Several changes to ensure reliability and avoid review noise are now in PureType’s GitHub reviewer:
review state - “approved” if no comments, “comment” if there are comments raised
no duplicate reviews - if GitHub shows that PureType has already reviewed the current branch and there are no further changes to files, no further review will be performed
draft pull requests ignored - PureType will not interact with pull requests in a draft state
multi-line comments are now fully supported
no duplicate comments - the GitHub reviewer now avoids duplicate comments, regardless if the previous comment thread is open or closed
August 20th 2024
There are now three types of GitHub reviewer modes, configurable during onboarding:
Automatic - review whenever a PR is opened, marked as ready for review, or new commits are synchronised to the branch
User review assignment - review whenever colleagues are assigned to the PR for review
Manual - use the /puretype review command in a GitHub comment to trigger a review
August 20th 2024
You can now self-onboard onto PureType!
There is now a onboarding component that is displayed on the “My Knowledge” page when not all onboarding steps have been completed.
This project involved several other supporting changes:
GitHub app - the GitHub app installation flow now:
maps from GitHub installation and user to PureType user automatically
present settings for GitHub reviewer behaviour
removes configuration when the app is uninstalled on a particular organisation
Notification settings - you can now configure notification settings on initial setup, to be reminded in the way that most suits your daily workflow
August 13th 2024
Several changes to the extension following recent onboarding testing:
present the authentication dialog on logout
show error on missing access token
depend on the ElixirLS extension to provide the elixir filetype for now
address issues with websocket error reporting
basic Sentry setup for error reporting