-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
fix: Updated RepoChecker to allow all types of repos #202
Conversation
submitting for review
Co-authored-by: Brian Douglas <[email protected]>
Co-authored-by: Brian Douglas <[email protected]>
Co-authored-by: Brian Douglas <[email protected]>
Co-authored-by: Brian Douglas <[email protected]>
Co-authored-by: Brian Douglas <[email protected]>
Co-authored-by: Brian Douglas <[email protected]>
(i hate lint)
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.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
Protected Branch
In order to be considered for merging, the pull request changes must not be implemented on the "beta" branch. This is described in our Contributing Guide. We would suggest that you close this PR and implement your changes as described in our Contributing Guide and open a new pull request.
The change looks good, but you should probably give this a read - https://docs.github.com/en/get-started/quickstart/github-flow. You should keep your beta branch up to date, check out feature branches from that branch, and then open pull requests. This will help you work on multiple stuff, keep your commit history clean and is best practice. Anyway, we squash commits so it doesn't matter in this case, but good to keep in mind for later! |
Need to rebase |
Checking again. Can you run the following
|
uh, sorry for being unavailable. i don't have my laptop with me right now. I'll get to this tomorrow. |
its working now @bdougie |
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.
Thanks for rebasing
## [1.10.0-beta.3](v1.10.0-beta.2...v1.10.0-beta.3) (2023-07-11) ### π Bug Fixes * Rename project-utilities.md to 3-project-utilities.md ([d0a6702](d0a6702)) * Updated RepoChecker to allow all types of repos ([#202](#202)) ([2161918](2161918)), closes [issue#112](https://github.com/open-sauced/issue/issues/112) [issue#112](https://github.com/open-sauced/issue/issues/112)
π This PR is included in version 1.10.0-beta.3 π The release is available on GitHub release Your semantic-release bot π¦π |
## [1.10.0](v1.9.0...v1.10.0) (2023-07-12) ### π Features * Cherry pick susmita ([#204](#204)) ([7458724](7458724)) * react/unreact on highlights ([#200](#200)) ([c65eca0](c65eca0)) ### π Bug Fixes * Create issue-metrics.yml ([4a6c19d](4a6c19d)) * Rename project-utilities.md to 3-project-utilities.md ([d0a6702](d0a6702)) * Updated RepoChecker to allow all types of repos ([#202](#202)) ([2161918](2161918)), closes [issue#112](https://github.com/open-sauced/issue/issues/112) [issue#112](https://github.com/open-sauced/issue/issues/112)
π This PR is included in version 1.10.0 π The release is available on GitHub release Your semantic-release bot π¦π |
## [1.10.0-beta.3](open-sauced/ai@v1.10.0-beta.2...v1.10.0-beta.3) (2023-07-11) ### π Bug Fixes * Rename project-utilities.md to 3-project-utilities.md ([d0a6702](open-sauced/ai@d0a6702)) * Updated RepoChecker to allow all types of repos ([#202](open-sauced/ai#202)) ([2161918](open-sauced/ai@2161918)), closes [issue#112](https://github.com/open-sauced/issue/issues/112) [issue#112](https://github.com/open-sauced/issue/issues/112)
## [1.10.0](open-sauced/ai@v1.9.0...v1.10.0) (2023-07-12) ### π Features * Cherry pick susmita ([#204](open-sauced/ai#204)) ([7458724](open-sauced/ai@7458724)) * react/unreact on highlights ([#200](open-sauced/ai#200)) ([c65eca0](open-sauced/ai@c65eca0)) ### π Bug Fixes * Create issue-metrics.yml ([4a6c19d](open-sauced/ai@4a6c19d)) * Rename project-utilities.md to 3-project-utilities.md ([d0a6702](open-sauced/ai@d0a6702)) * Updated RepoChecker to allow all types of repos ([#202](open-sauced/ai#202)) ([2161918](open-sauced/ai@2161918)), closes [issue#112](https://github.com/open-sauced/issue/issues/112) [issue#112](https://github.com/open-sauced/issue/issues/112)
What type of PR is this? (check all applicable)
Description
Update the regular expression in
isGithubRepoPage
function inurlMatchers.ts
to include an optional trailing slash in the GitHub repository URL. This allows URLs with or without a trailing slash to be recognized as GitHub repository pages.Related Tickets & Documents
#176
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?