-
Notifications
You must be signed in to change notification settings - Fork 706
[CURITIBA-2026] Add initial event information #15564
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for devopsdays-web ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hey there, @esaito! There have been some changes requested that need to be addressed before we can merge this for you. Please let us know if you need help. |
|
from: Emerson Saito [email protected] |
toshywoshy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are also making changes to the 2025 event, I don't think that is what you want to do in a 2026 PR
phrawzty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I confirm that the 📧 was received and everything is in order.
However, I agree with @toshywoshy that the modifications to 2025-curitiba should not be in this PR. Please modify only 2026 in this PR; a new PR should be created for edits to any other years, respectively.
Initial setup for Curitiba 2026 event: