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

Add Support for SpiderHeck #146

Merged
merged 4 commits into from
Jul 22, 2024
Merged

Add Support for SpiderHeck #146

merged 4 commits into from
Jul 22, 2024

Conversation

mgilardi
Copy link
Contributor

@mgilardi mgilardi commented Apr 6, 2024

Hey there, @Z1ni! I added this for myself in my own fork (and verified it works), so I thought I'd create a PR to get it upstream in case it helps anyone in the future. Feel free to do with the PR as you please. :)

Also... Thanks so much for creating this tool. It was beyond helpful.

@Z1ni
Copy link
Owner

Z1ni commented Jul 2, 2024

Thanks for the PR, and I'm glad that the tool was helpful!

I tried to resolve the README conflict using GitHub UI, but it created an ugly merge commit and now the UI doesn't let me rebase-merge this 😅

Can you please rebase your forked branch and throw away my merge commit (or just create a new branch and a new pull request if that's easier for you)? Thanks!

@mgilardi
Copy link
Contributor Author

mgilardi commented Jul 5, 2024

@Z1ni Should be good to merge now 😄 if you wanted to squash my commit when you merge, it should get rid of the unsightly commits but still retain attribution and history via the PR link in the squash merge title.

For example, a squashed commit would read something like:
Add Support for SpiderHeck (#146)

@Z1ni Z1ni merged commit 5569ead into Z1ni:main Jul 22, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

2 participants