Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
GitHub Action
See original GitHub issueHello! Thank you for creating this excellent tool. It has already saved me many hours!
I have created a GitHub Action to automatically run this project, and push the output to a GitHub repo. This allows users to maintain a git version controlled copy of all the components, and for it to keep itself up-to-date.
It also supports the .env file for this project, so you can run all your transformers, and login info is kept securely in secrets.
I’d appreciate any feedback/input/questions you might have, and would love to put this somewhere on your README.md, if you think it could help others.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Awesome. I’m glad you are finding it useful. If you want to add it to the README, send me a PR and I’ll merge it.
I’m lazy so I’m always looking for ways to automate repetitive tasks.
I’ve been working on a workflow for keeping track of my custom React components. Basically I add a comment to my component with the commit hash of the original file. Then when I get the latest updates, I have a script that will tell me which files were changed and what component I need to check. After I make any changes, I update the hash, ready for the next update.
Adam makes a bunch of CSS tweaks so I want to keep my components in sync as much as possible.
@GregBrimble no trick - your instructions in the readme were correct! It was a mistake on my part…thank you!