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

Allow customizing the source string generated in the wiki #136

Open
LiamBull opened this issue Jan 23, 2025 · 2 comments
Open

Allow customizing the source string generated in the wiki #136

LiamBull opened this issue Jan 23, 2025 · 2 comments

Comments

@LiamBull
Copy link

LiamBull commented Jan 23, 2025

It would be great to be able to change the format of the source generated in the wiki to use the typical SSH format.

eg: [email protected]:techpivot/terraform-module-releaser.git rather than git::https://github.com/techpivot/terraform-module-releaser.git

I am about to submit a PR that adds a quick and dirty implementation, just to give an idea. I am not a TypeScript guy or overly familiar with the codebase so this isn't meant to be an all encompassing thing, but hopefully a good place to start if you agree with this issue.

PR: #137

@virgofx
Copy link
Member

virgofx commented Jan 23, 2025

Hi @LiamBull Great suggestion and I think it makes perfect sense. I just quickly browsed the PR and it's pretty close to what I'd do. I believe the only other thing I would do is add some testing for it to test both sides as I was able to get 100% test coverage. I'm happy to merge yours (unreleased) and then add the tests on top if that works? Alternatively, if you wanted to try and get some tests working I'm happy to let you drive this effort?

Edit: Appears I may have a token issue in the latest CI somewhere so I'll need to work on a few things somewhere first!

@LiamBull
Copy link
Author

I'm happy to merge yours (unreleased) and then add the tests on top if that works?

By all means, go for it. If you haven't gotten to it by next week, I should have some time to tackle it.

Appears I may have a token issue in the latest CI somewhere so I'll need to work on a few things somewhere first!

I'll wait until you reply here that you've fixed the CI before I do anything.

Greatly appreciate the quick response @virgofx!

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