Skip to content

Portland: Add event on Feb 28th#68

Merged
tristanpemble merged 2 commits intokristoff-it:mainfrom
tristanpemble:zdp2
Feb 7, 2026
Merged

Portland: Add event on Feb 28th#68
tristanpemble merged 2 commits intokristoff-it:mainfrom
tristanpemble:zdp2

Conversation

@tristanpemble
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@MasonRemaley MasonRemaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@MasonRemaley
Copy link
Collaborator

Not sure what's causing this CI failure, gonna run it on master to make sure it's not related to these changes somehow?

@tristanpemble
Copy link
Collaborator Author

secrets.AUTOMERGE_KEY seems to be blank, but it was last edited 6 months ago, and recent PRs passed, so I don't understand what changed

@tristanpemble
Copy link
Collaborator Author

@MasonRemaley I think it's because I opened this from a fork instead of the base repository, and it's a repo permissions issue. all the recently passing PRs were created from branches on this repository

@tristanpemble tristanpemble merged commit e4601c4 into kristoff-it:main Feb 7, 2026
2 of 4 checks passed
@tristanpemble tristanpemble deleted the zdp2 branch February 7, 2026 22:32
@MasonRemaley
Copy link
Collaborator

@kristoff-it heads up that we got a CI failure here on the codeowners check presumably due to the way the PR was created, seems safe to merge since the error should essentially vanish once this PR is merged. Let me know if this ends up causing any problems.

@tristanpemble
Copy link
Collaborator Author

@MasonRemaley @kristoff-it deployment was successful https://zig.day/usa/portland/2/

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