-
Notifications
You must be signed in to change notification settings - Fork 0
Add remote repository URL #2
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: develop
Are you sure you want to change the base?
Conversation
Updated the build dependencies step in the Windows workflow.
Create xrp package json
📝 WalkthroughWalkthroughThree distinct changes were introduced: a GitHub Actions workflow YAML file was modified with malformed syntax in its Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 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.
Actionable comments posted: 3
🤖 Fix all issues with AI agents
In @.github/workflows/windows.yml:
- Around line 105-107: The workflow YAML was corrupted by inserting a Markdown
badge where the `with:` mapping belongs; revert that line so `with:` is a proper
mapping key and ensure `configuration: ${{ matrix.configuration.type }}` is
indented under it (i.e., put `with:` on its own line and follow with the
`configuration:` entry as a child of `with:`). Remove the markdown badge text
entirely from this block and restore the original mapping structure so
actionlint/GitHub can parse the workflow.
In `@git`@github.com:JSTONE1111/rippled.git:
- Line 1: Delete the accidental file whose entire content is the single string
"[email protected]:JSTONE1111/rippled.git": remove it from the working tree and
commit the deletion (git rm <file>; git commit -m "Remove accidental git URL
file"); if the file was part of a pushed commit and must be purged from history,
use an interactive rebase or git filter-repo to remove it and force-push the
cleaned branch; optionally add a .gitignore entry to prevent re-adding such
stray files.
In `@xrp` package json:
- Around line 1-16: This package.json (project name "xrpl-dev-boilerplate")
doesn't belong in the rippled repo; remove the added package.json file from the
PR and any unrelated Node.js boilerplate artifacts (references to index.js,
scripts.start, scripts.dev, and dependencies like
express/body-parser/dotenv/xrpl). If you actually intend to add a Node project,
move this package.json into the correct separate repository and ensure
scripts.dev references nodemon only if nodemon is declared in devDependencies;
otherwise add nodemon to devDependencies. Ensure no stray Node files remain in
the rippled changeset.
| with:[](https://github.com/JSTONE1111/rippled/actions/workflows/levelization.yml) | ||
|
|
||
| configuration: ${{ matrix.configuration.type }} |
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.
Critical: Malformed YAML breaks the entire Windows CI workflow.
Line 105 replaces the valid with: mapping with a Markdown badge link, producing invalid YAML. The actionlint static analysis tool also flags this: could not parse as YAML: could not find expected ':'. This will prevent the workflow from being parsed by GitHub Actions, so no Windows CI jobs will run.
🐛 Proposed fix — restore valid YAML
- with:[](https://github.com/JSTONE1111/rippled/actions/workflows/levelization.yml)
-
+ with:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| with:[](https://github.com/JSTONE1111/rippled/actions/workflows/levelization.yml) | |
| configuration: ${{ matrix.configuration.type }} | |
| with: | |
| configuration: ${{ matrix.configuration.type }} |
🧰 Tools
🪛 actionlint (1.7.10)
[error] 105-105: could not parse as YAML: could not find expected ':'
(syntax-check)
🪛 YAMLlint (1.38.0)
[error] 107-107: syntax error: could not find expected ':'
(syntax)
🤖 Prompt for AI Agents
In @.github/workflows/windows.yml around lines 105 - 107, The workflow YAML was
corrupted by inserting a Markdown badge where the `with:` mapping belongs;
revert that line so `with:` is a proper mapping key and ensure `configuration:
${{ matrix.configuration.type }}` is indented under it (i.e., put `with:` on its
own line and follow with the `configuration:` entry as a child of `with:`).
Remove the markdown badge text entirely from this block and restore the original
mapping structure so actionlint/GitHub can parse the workflow.
| @@ -0,0 +1 @@ | |||
| [email protected]:JSTONE1111/rippled.git | |||
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.
Remove this file — it serves no purpose and appears to be an accidental commit.
A file whose name and sole content is a git SSH remote URL ([email protected]:JSTONE1111/rippled.git) does not belong in the repository. This looks like an accident (e.g., a shell redirect or mistyped command).
🤖 Prompt for AI Agents
In `@git`@github.com:JSTONE1111/rippled.git at line 1, Delete the accidental file
whose entire content is the single string
"[email protected]:JSTONE1111/rippled.git": remove it from the working tree and
commit the deletion (git rm <file>; git commit -m "Remove accidental git URL
file"); if the file was part of a pushed commit and must be purged from history,
use an interactive rebase or git filter-repo to remove it and force-push the
cleaned branch; optionally add a .gitignore entry to prevent re-adding such
stray files.
| { | ||
| "name": "xrpl-dev-boilerplate", | ||
| "version": "1.0.0", | ||
| "description": "XRPL dev boilerplate — wallet generation, balance, payment example (Testnet)", | ||
| "main": "index.js", | ||
| "scripts": { | ||
| "start": "node index.js", | ||
| "dev": "NODE_ENV=development nodemon index.js" | ||
| }, | ||
| "dependencies": { | ||
| "body-parser": "^1.20.2", | ||
| "dotenv": "^16.3.1", | ||
| "express": "^4.18.2", | ||
| "xrpl": "^4.4.0" | ||
| } | ||
| } No newline at end of file |
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.
This package.json does not belong in the rippled repository.
rippled is a C++ implementation of the XRP Ledger server. A Node.js boilerplate project (xrpl-dev-boilerplate) with Express/body-parser/dotenv dependencies is unrelated and should not be added to this repository. There is also no corresponding index.js or any application code in this PR.
Additionally, the dev script references nodemon but it is not listed in dependencies or devDependencies.
🤖 Prompt for AI Agents
In `@xrp` package json around lines 1 - 16, This package.json (project name
"xrpl-dev-boilerplate") doesn't belong in the rippled repo; remove the added
package.json file from the PR and any unrelated Node.js boilerplate artifacts
(references to index.js, scripts.start, scripts.dev, and dependencies like
express/body-parser/dotenv/xrpl). If you actually intend to add a Node project,
move this package.json into the correct separate repository and ensure
scripts.dev references nodemon only if nodemon is declared in devDependencies;
otherwise add nodemon to devDependencies. Ensure no stray Node files remain in
the rippled changeset.
High Level Overview of Change
Context of Change
Type of Change
.gitignore, formatting, dropping support for older tooling)API Impact
libxrplchange (any change that may affectlibxrplor dependents oflibxrpl)Summary by CodeRabbit