Repository navigation
Proposal: add a small CI check for Python syntax and README links #310
Closed
sanaullahcode
started this conversation in
Show and tell
Replies: 1 comment
|
LargestNumberAfterMutatingSubtring ko LargestNumberAfterMutatingSubstring karo README line 13 mein ./algorithms/cpp/leetcode/sumOfDigits... ko ./algorithms/cpp/sumOfDigits... karo |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
While reading the repo I ran two quick checks and both found problems.
py_compile on all Python files found 1 file that cannot run (see issue #)
Checking every relative link in README.md found 2 of 653 pointing to paths that do not exist
Problem 1946 Java link has a typo in the folder name LargestNumberAfterMutatingSubtring
Problem 1945 C++ link has an extra leetcode/ folder in the path
Both would have been caught automatically. I would like to propose a tiny GitHub Actions workflow that runs on pull requests and does only these things
python -m compileall algorithms/python
A short script that verifies relative links in README.md exist
It adds no dependencies and keeps the repo easy for contributors. I can write the workflow and the link script and open a PR if this sounds useful. Any objections or preferences first?
Steps
Fork the repo then clone it
git checkout -b fix/max-average-subarray-python
Apply fix: git apply fix-findMaxAverage.patch
git commit -am "Fix IndentationError in MaximumAverageSubarrayI python solution"
Push then open the PR. Issue pehle file karo taake Fixes #N link ho jaye
All reactions