-
Notifications
You must be signed in to change notification settings - Fork 9
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
Misc tasks to fork #2
Conversation
@cspotcode Hey 👋 |
@LironHazan good idea, I don't remember, but I do not think I checked if they were passing in the origin repo. If you would like to be a collaborator on this repo, let me know and I can add you. It will give you permission to push to this branch directly. |
@cspotcode thanks, I'll be happy to collaborate, btw in future thinking of modern stack, would we want to use eslint instead of tslint? (TSLint has been deprecated in favor of ESLint. Please see palantir/tslint#4534 for more information.) |
I have added you as a collaborator so you should have access to triage issues and pull requests and push code. |
prettier is great, I tend to combine both :) Thanks! |
@cspotcode I've ran the tests in origin branch they passed so I've noticed following commit: TOTAL: 233 SUCCESS Finished in 0.729 secs / 0.239 secs @ 21:05:33 GMT+0300 (Israel Daylight Time) SUMMARY: pushing changes |
@cspotcode sorry to nudge, not sure what happened, the git actions weren't on the fork-tasks local branch so I got them back from upstream/master, I don't see it hooked on commit at the moment |
Codecov Report
@@ Coverage Diff @@
## master #2 +/- ##
=========================================
Coverage ? 93.41%
=========================================
Files ? 34
Lines ? 653
Branches ? 80
=========================================
Hits ? 610
Misses ? 30
Partials ? 13 Continue to review full report at Codecov.
|
Awesome, if you think this pull request is ready to merge, go for it. |
@cspotcode sure so I'll merge and will branch out to a "tasks-3" branch which will contain some new configs, wdyt? |
I think we can name the branches according to the changes in them, like We may want to postpone large stylistic changes if they make it more difficult to merge existing pull requests from the NagRock and johanblumenberg repositories. |
|
No description provided.