Move files out of root directory to highlight README (#571)#933
Open
SurbhiAgarwal1 wants to merge 1 commit into
Open
Move files out of root directory to highlight README (#571)#933SurbhiAgarwal1 wants to merge 1 commit into
SurbhiAgarwal1 wants to merge 1 commit into
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (18)
Summary by CodeRabbit
WalkthroughAll build tooling is updated to reflect that the frontend project lives under ChangesPath relocation across build tooling
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Contributor
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
REPO="OWASP/OpenCRE"
PR=933
echo "=== PR Status ==="
gh pr view $PR --repo $REPO --json state,mergeable,mergeStateStatus,reviewDecision,isDraft,title,baseRefName,headRefName
echo ""
echo "=== CI Checks ==="
gh pr checks $PR --repo $REPO 2>&1 || true
echo ""
echo "=== Reviews ==="
gh pr view $PR --repo $REPO --json reviews
echo ""
echo "=== Review Comments (unresolved) ==="
gh api "repos/$REPO/pulls/$PR/comments" --jq '[.[] | {id:.id, user:.user.login, body:.body, path:.path, line:.line}]' 2>&1 | head -100
echo ""
echo "=== Issue Comments ==="
gh api "repos/$REPO/issues/$PR/comments" --jq '[.[] | {id:.id, user:.user.login, body:.body[0:200]}]' 2>&1 | head -100Length of output: 1551
The only blocker is that the PR has |
Contributor
|
Tip For best results, initiate chat on the files or code changes. Let me look up the repository maintainers so I can tag the right people. #!/bin/bash
set -euo pipefail
REPO="OWASP/OpenCRE"
echo "=== Repository collaborators/contributors ==="
gh api "repos/$REPO/contributors" --jq '[.[] | {login:.login, contributions:.contributions}] | sort_by(-.contributions) | .[0:10]'
echo ""
echo "=== CODEOWNERS or maintainers file ==="
gh api "repos/$REPO/contents/CODEOWNERS" --jq '.content' 2>/dev/null | base64 -d 2>/dev/null || echo "No CODEOWNERS file found"
echo ""
echo "=== Recent PR reviewers ==="
gh api "repos/$REPO/pulls?state=closed&per_page=10" --jq '[.[] | {number:.number, reviewers:[.requested_reviewers[].login]}]'
echo ""
echo "=== Repo topics/details ==="
gh repo view $REPO --json owner,assignees
echo ""
echo "=== Issue `#571` details (linked issue) ==="
gh api "repos/$REPO/issues/571" --jq '{title:.title, assignees:[.assignees[].login], author:.user.login}'
</thinking>
```shell
#!/bin/bash
set -euo pipefail
REPO="OWASP/OpenCRE"
PR=933
echo "=== PR Requested Reviewers ==="
gh pr view $PR --repo $REPO --json requestedReviewers
echo ""
echo "=== Top contributors ==="
gh api "repos/$REPO/contributors" --jq '[.[] | {login:.login, contributions:.contributions}] | sort_by(-.contributions) | .[0:8]'
echo ""
echo "=== Repo admins/org members ==="
gh api "repos/$REPO/collaborators" --jq '[.[].login]' 2>/dev/null || echo "Cannot list collaborators (private info)" |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR addresses issue #571 by decluttering the repository's root directory, ensuring the
README.mdand primary entry points are significantly more prominent. Configuration files have been organized into their respective logical subdirectories, specifically separating frontend tooling from backend dependencies.What was changed:
application/frontend/.package.json,yarn.lock,.babelrc,.eslintrc.js,.prettierrc,.prettierignore,tsconfig.json,webpack.config.js,webpack.prod.js,cypress.json,enzyme-setup.jsapplication/.requirements.txt,pytest.iniAGENTS.mdtodocs/AGENTS.mdCODE_OF_CONDUCT.mdto.github/CODE_OF_CONDUCT.mdMakefile: Updated commands to executeyarnscripts from within theapplication/frontenddirectory, and updated thepip installpath forrequirements.txt.Dockerfile&Dockerfile-dev: Updated theCOPYandRUNdirectives to ensure dependencies are installed correctly from the new subdirectory paths..github/workflows/linter.yml): Updated the CI linting job tocd application/frontendbefore installing dependencies and checking formatting.(Note: Essential standard files such as
README.md,LICENSE,Makefile,.gitignore, and.dockerignorewere explicitly left in the root directory as they are required by platforms like GitHub and Docker.)Testing Performed:
make testequivalent) to verify that internal logic and paths remain intact.DockerfileandMakefilecorrectly reflect the newly nested structures.Closes #571