-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: add HEAD
handler
#9753
feat: add HEAD
handler
#9753
Conversation
🦋 Changeset detectedLatest commit: 93fb961 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@s3812497 it looks like this PR will need a rebase |
This reverts commit a580ed4.
092729d
to
da33e52
Compare
Thanks for the reminder @benmccann . I've just learnt what a rebase is. I did a merge before that (hence the force push trying to undo that). Will use rebase from now on. |
Oh, I just use the term rebase out of habit. But really I think folks prefer if you do a merge because if they have the code checked out it's easier to pull a merge |
@s3812497 this has a merge conflict - can you look at it today? Else I'll look into it later. |
Sure thing! I'll have a look at it now. |
I wonder if we'd want some sort of fallback implementation which executes |
That fallback already exists today, and will still apply if you don't define the |
closes #9468
Allows exporting the
HEAD
handler. Not sure if language-tools needs to be updated to remove the error message for this as well.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.