-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: standardize repository for procore open-source #2
Conversation
6ca6040
to
ed5ecf7
Compare
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
712969e
to
1b2dee8
Compare
- [x] setup .github folder (actions, dependabot.yaml, ISSUE_TEMPLATES, PULL_REQUEST_TEMPLATE.md, CODEOWNERS) - [x] add procore-oss/procore-rspec-profiling team to CODEOWNERS - [x] setup required files (README.md, SECURITY.md, CODE_OF_CONDUCT.md, LICENSE.md, CONTRIBUTING.md) - [x] update gemspec file - [x] setup postgres in tests in GitHub actions - [x] test against postgres bookworm versions - [x] add EMERITUS mentioning former upstream contributors - [x] update LICENSE.md with previous owners - [x] setup dummy rails app in specs folder Signed-off-by: jmeridth <[email protected]> Co-authored-by: Steven Johnson <[email protected]> Co-authored-by: Bob Laskowski <[email protected]>
d26777f
to
41178e5
Compare
should we update the |
@pc-bob yes, after this merges IMO. Updating description with further PR changes after this merges. |
Next PRs after this:
Checklist: