This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
Slack Block Kit UI for Daily GitHub Summary #253
Merged
alysivji
merged 22 commits into
busy-beaver-dev:master
from
alysivji:revamp-github-summary-ui
Apr 18, 2020
Merged
Slack Block Kit UI for Daily GitHub Summary #253
alysivji
merged 22 commits into
busy-beaver-dev:master
from
alysivji:revamp-github-summary-ui
Apr 18, 2020
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this do
Slack Block Kit is a UI framework for building native Slack experiences.
We were posting Daily GitHub Summary reports in Markdown. Porting over current functionality to Block Kit will make it easier to improve things down the line.
Also got a few other things done
set_task_progress
referencesdocker-compose.prod.yaml
Why are we doing this
Want to take advantage of newer Slack features
How should this be tested
Changed internals, end-to-end functionality is the same. Although I'm not quite sure how to test Slack Block kit. Maybe jest-esque tests?
Migrations
n/a
Dependencies
n/a
Callouts