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

Removing Node Resolver #300

Closed
wants to merge 7 commits into from
Closed

Removing Node Resolver #300

wants to merge 7 commits into from

Conversation

quintessence
Copy link
Contributor

Description of the change
Merges changed from PR #262 .

Which issue this PR fixes
PR #262 fixes GH Issue #263 .

quintessence and others added 7 commits February 23, 2024 14:40
Signed-off-by: Quintessence <quintessenceanx@gmail.com>
Signed-off-by: Quintessence <github@agirlhasnona.me>
Signed-off-by: Quintessence <github@agirlhasnona.me>
Signed-off-by: Quintessence <github@agirlhasnona.me>
Signed-off-by: Quintessence <github@agirlhasnona.me>
Signed-off-by: Quintessence <github@agirlhasnona.me>
Copy link

netlify bot commented Mar 8, 2024

Deploy Preview for spiffe ready!

Name Link
🔨 Latest commit 448eb30
🔍 Latest deploy log https://app.netlify.com/sites/spiffe/deploys/65eba31a10e9e20008abdc9d
😎 Deploy Preview https://deploy-preview-300--spiffe.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@quintessence
Copy link
Contributor Author

For this PR - can we squash the commit since it pulled in a duplicate of the same HeadBucket commit. I'll delete and re-create my fork after, something weird must've happened when I tried to sync my fork.

@quintessence
Copy link
Contributor Author

Closing - see PR #299

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.

None yet

1 participant