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.
Support for Git aliases
See original GitHub issue🚀 Feature Proposal
Add support to Git aliases, and other Git features that are missing from meta-git.
Motivation
Some people (not sure how many but I’m one of them 😅) use Git aliases to ease up and speed up their development flow, by pretty much reimplementing the Git commands as done in meta-git we are missing this feature as we have to explicitly use the command that are redefined here.
This would also have the side effect of future proofing the package as we won’t need to do anything to support any newer Git commands.
Example
If for example you have the following in your ~/.gitconfig file
[aliases]
a = add
You should be able to run meta git a instead of meta git add.
This also goes for other more complex aliases that could be placed.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (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
I think it should just print out the commands a user can run to cleanup their workspace. I don’t think it should do anything destructive on the fs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.