-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
2025-04-28-pessa #189
base: main
Are you sure you want to change the base?
2025-04-28-pessa #189
Conversation
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
2 similar comments
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
2 similar comments
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
1 similar comment
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-pessa-189/blog/pessa/ ! |
OpenReview Submission Thread
Checklist before opening a PR
I am opening a pull request against the
main
branch of the2025
repo.My post and all associated references to it are all lowercase, i.e
The title of my PR is exactly the name of my markdown file
_posts/2025-04-28-[submission-name].md
would require a PR name2025-04-28-[submission-name]
I have anonymized my post: my author's list is
Anonymous
, and there is no potentialcontent which can reveal my/my collaborators identities.
My post matches the formatting requirements, including (but not limited to):
your PR automatically being closed!):
_posts/
with the format_posts/2025-04-28-[submission-name].md
(or.html
)assets/img/2025-04-28-[submission-name]/
assets/html/2025-04-28-[submission-name]/
assets/bibliography/2025-04-28-[submission-name].bib
description
field of my front-mattertoc
field of my front-matter.bibtex
file as per the sample postAny other comments