-
Notifications
You must be signed in to change notification settings - Fork 1
Separate obs4REF reference data from published obs4MIPs #82
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
Open
lewisjared
wants to merge
6
commits into
main
Choose a base branch
from
obs4mips-labelling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
61f3ead
feat: separate obs4REF reference data from published obs4MIPs
lewisjared ca0c333
fix: make the Biome pre-commit hooks actually work
lewisjared d26c114
docs: renumber the changelog fragment to the PR, and note the pre-com…
lewisjared 10b8230
docs: tighten the reference dataset source wording
lewisjared d549245
refactor: rename the reference dataset `source` field to `source_type`
lewisjared d0d8d56
docs: stop repeating pre-release in the reference dataset wording
lewisjared 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
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
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
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.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: Climate-REF/ref-app
Length of output: 157
🏁 Script executed:
Repository: Climate-REF/ref-app
Length of output: 5502
🌐 Web query:
Biome 2.2.4 CLI files ignoreUnknown unsupported Markdown files check documentation💡 Result:
In Biome, the
files.ignoreUnknownconfiguration option is used to control how the CLI handles files with extensions that Biome does not recognize [1][2]. By settingignoreUnknowntotruein yourbiome.jsonconfiguration file, you tell Biome to suppress diagnostic errors when it encounters unsupported file types [1]. If you are encountering errors when running Biome on unsupported files (such as Markdown files, if they are not explicitly supported or handled by your configuration), you can resolve this in the following ways: 1. Configuration File: Add the following to yourbiome.jsonfile [1]: { "files": { "ignoreUnknown": true } } 2. CLI Flag: You can also use the--files-ignore-unknownflag directly in your terminal command to achieve the same effect for a single execution [3][4]: biome check --files-ignore-unknown=true. If you continue to see errors such as "No files were processed in the specified paths," this is often expected behavior if Biome is configured to only look at specific files or if the input paths provided are entirely ignored [5][4]. In such cases, you may also want to use the--no-errors-on-unmatchedflag, which prevents the CLI from exiting with an error code if no files are matched by your provided patterns [5]. For more details on managing file inclusion and exclusion, you can refer to the official Biome configuration documentation [1][6].Citations:
🏁 Script executed:
Repository: Climate-REF/ref-app
Length of output: 9834
Prevent the Biome hook from scanning unsupported files.
biome check --writescans the wholefrontenddirectory.frontend/biome.jsonincludes unknown files and setsfiles.ignoreUnknowntofalse. Files such asfrontend/README.mdcan therefore make the hook fail when a matching file triggers it. Remove unsupported extensions from the hook trigger or setfiles.ignoreUnknowntotrue.Source: MCP tools