-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
Gitcoin Updates modal #5016
Gitcoin Updates modal #5016
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5016 +/- ##
=======================================
Coverage 30.92% 30.92%
=======================================
Files 217 217
Lines 17402 17402
Branches 2381 2381
=======================================
Hits 5382 5382
Misses 11801 11801
Partials 219 219 Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #5016 +/- ##
==========================================
+ Coverage 30.93% 31.47% +0.54%
==========================================
Files 217 218 +1
Lines 17457 18870 +1413
Branches 2392 2847 +455
==========================================
+ Hits 5400 5939 +539
- Misses 11836 12645 +809
- Partials 221 286 +65
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think using a Gist for this is cool, but is there another place we can put it that's easier to manage? I just worry since theres no shared ownership for gists (I don't think...) so only @octavioamu can update it.
@danlipert yes agree, there is not shared management of gists. Should we create it in our database instead? There is other external tool we can use for that? I was checking maybe gh wikis ? |
Yeah the Github Wiki could work
…-Dan Lipert
On Wed, Aug 21, 2019 at 2:57 AM Octavio Amuchástegui < ***@***.***> wrote:
@danlipert <https://github.com/danlipert> yes agree, there is not shared
management of gists. Should we create it in our database instead? There is
other external tool we can use for that? I was checking maybe gh wikis ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5016?email_source=notifications&email_token=AAGUHEVNGMRG3BDGUKZTD6DQFQV7XA5CNFSM4ILQ32L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4XEPZI#issuecomment-523126757>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGUHEQWRAVIPX76XM4L6DLQFQV7XANCNFSM4ILQ32LQ>
.
|
Looks solid ! adding a don't merge label until we have content figured out to throw into the wiki ❤️ |
looks like wiki are not available by gh API https://github.community/t5/How-to-use-Git-and-GitHub/API-for-repository-s-wiki/td-p/6706 |
ok found a better way, now is an issue #5057 |
This good to merge today? What do y'all think? @octavioamu @thelostone-mc |
Description
All the content is from a Gist file, so can be updated in any moment.
I created some rules to not affect performance or be annoying with the users:
Refers/Fixes
Fix #4896
Testing
https://embed.vidyard.com/share/DfE1gP7mvRvSh6e79DLNDF