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

Investigate using Backstroke to track changes to fork source #24

Open
chrisbolin opened this issue Jun 5, 2018 · 2 comments
Open

Investigate using Backstroke to track changes to fork source #24

chrisbolin opened this issue Jun 5, 2018 · 2 comments

Comments

@chrisbolin
Copy link
Contributor

chrisbolin commented Jun 5, 2018

tip from @marcelmokos:

Since this is a fork we can use https://backstroke.co/ to track changes in the source project.

(in #22)

@ryan-roemer
Copy link
Member

We've also diverged from upstream with things like test locations etc. Will need to get a handle on how backstroke handles this.

Also, what the heck is this emoji on backstroke/server?

screen shot 2018-06-05 at 7 47 22 am

THAT'S NOT BACKSTROKE

@chrisbolin
Copy link
Contributor Author

yeah, honestly i'd really just like something like greenkeeper.io, but fast-deep-equal isn't in dependencies (nothing is), and there are a lot of things in devDependencies which would just create noise. i'll look into this if there's a nice simple config

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

No branches or pull requests

2 participants