-
Notifications
You must be signed in to change notification settings - Fork 163
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
fix: 🐛 create default version value for forked repos #2303
fix: 🐛 create default version value for forked repos #2303
Conversation
this change allows people who are trying to contribute to LPython to build the project locally without having to manually create a tag or fetch from origin
I would not do it by default like this, as I think we want to see the error message if something goes wrong with the tags. Rather, why not creating a separate script for this? |
@certik good point. I assumed that, unlike the forked ones, the upstream repo will always have the configured tags but an error might indeed occur. I will undo changes in |
(Usually that is the case. But I've seen sometimes if the tags don't download for some reason, such as in your fork, then we want to see it break.) |
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 that works!
Thanks! |
It would be helpful to mention this in the readme: https://github.com/lcompilers/lpython#linux-and-macos |
@abhi-glitchhg go ahead and submit a PR to the README. Thanks! |
Related issue
This change allows people who are trying to contribute to LPython to build the project locally without having to manually create a tag or fetch from origin.
The local build will default to
0.0.0-0