-
Notifications
You must be signed in to change notification settings - Fork 338
hellovai/beps/exceptions #2759
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
Merged
Merged
hellovai/beps/exceptions #2759
Changes from 19 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
9ceed11
Initial research
hellovai f0cb411
Adding readme
hellovai 75ba816
upate readme
hellovai 7863ce6
add more comparisons (try-catch, go2 proposal)
hellovai 80c29dc
adding ambiguity of open questions
hellovai 2285593
add an updates section on the doc
hellovai 0067ef1
add match statement as well
hellovai 17d376d
update readme
hellovai 62dd494
better ideas for catch
hellovai 0a77b82
update readme
hellovai dc6877b
add coloring semantics
hellovai 8e92cff
adding story basis
hellovai 967761a
updating beps
hellovai fee6552
update readme
hellovai f846bc3
updating statuses
hellovai 9caba6c
improvements to content
hellovai fda19f5
updated readme
hellovai 3ea9af2
update bep?
hellovai 924d786
improve beps
hellovai 32ad26f
add slack notification
hellovai 9d221e0
fix
hellovai cd9a6cd
fixes for top level things
hellovai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Bug: Shallow clone breaks git history lookup in check script
The removal of
fetch-depth: 0from thecheck-bepsjob causes a shallow clone (depth 1 by default). Theupdate_bep_readme.py --checkscript runsgit log {canary_ref}..HEADto determine file modification dates, which requires commit history between canary and HEAD. With a shallow clone, this history is unavailable, causing the script to incorrectly return "TBD" forlast_modifieddates instead of actual values, leading to potential check failures or inconsistent behavior between CI and local development.