-
Notifications
You must be signed in to change notification settings - Fork 33
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
Custom release options. #45
Comments
@acalcutt - same issue. Currently im checking out the |
I'm encountering an issue with the node-pre-gyp-github package when trying to publish a release. The error message indicates that the target_commitish field is hardcoded to master, which causes a validation failure since my repository's default branch is main. Error Message:
|
This gets set at https://github.com/bchr02/node-pre-gyp-github/blob/master/index.js#L67 . In my fork @acalcutt/node-pre-gyp-github I changed this to 'main' because that is what maplibre-native uses and I was getting a similar error because of that. In my opinion it would be nice for 'node-pre-gyp-github' to read the branch from a new value in package.json. It would be helpful because right now you can use the package with other branches, but the tag always targets the 'main' or 'master' branch. This is annoying when trying to compare releases since it is targeting the wrong branch. Then it could be read it in as part of the init I also made a pre-release flag that looks for 'pre' in the version so it could automatically create a pre-release on github https://github.com/acalcutt/node-pre-gyp-github/blob/master/index.js#L75 |
I am using this plugin for maplibre-gl-native releases and right now I have had to make my own fork to customize several release options. I am mainly changing name/target_commitish and made a toggle for prerelease based on name at https://github.com/acalcutt/node-pre-gyp-github/blob/8f505b52c1cc794b7aa273dc22c542c6fc739ada/index.js#L64-L75.
I was wondering if the code here could be changed in a way that someone could set these options so a custom release wouldn't be necessary. maybe a few more options in the package.json configuration..or something like that.
The text was updated successfully, but these errors were encountered: