-
Notifications
You must be signed in to change notification settings - Fork 0
Update GitHub-related Documentation #61
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
Conversation
Why these changes are being introduced: With the updates to user permissions/privileges/roles in our GitHub Organization, it was time to update our developer documentation to reflect these changes. How this addresses that need: * Update the GitHub documentation, including the additional information about owners versus members and repository roles * Fix other slightly-outdated information in other files Side effects of this change: None.
0b40fc0 to
efa5a62
Compare
Why these changes are being introduced: The previous push to GitHub failed tests because of very outdated versions in the workflows. How this addresses that need: * Update the setup-python action to v4 (from v1) in the workflows * Update the python version to 3.12 (from 3.7) in the workflows * Update the python version to 3.12 in the Pipfile and update Pipfile.lock Side effects of this change: I have no idea yet!
efa5a62 to
20d2b1c
Compare
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.
Many of my suggestions are based on some auto formatting you did and not part of your intended changeset. If you'd prefer not to deal with them in this changeset please let me know so I can take care of them separately.
|
|
||
| We use [Code Climate](https://codeclimate.com/)'s GitHub integration to monitor | ||
| for code smells. Code Climate is free for open source repositories. | ||
| We use [Code Climate](https://codeclimate.com/)'s GitHub integration to monitor for code smells. Code Climate is free for open source repositories. |
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.
I don't think this is a broad truth in our org anymore and only EngX seems to be using it. It's also gotten really weird in the past few weeks as they are rolling out a replacement product.
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.
I'll leave this for another commit by you or someone else.
| repos may still use `master` and should be migrated. GitHub now provides an | ||
| easy way to do this in the web UI. In the repo's settings, you can | ||
| change the name of the default branch. | ||
| While all new repos will be created with `main` as the default branch, older repos may still use `master` and should be migrated. GitHub now provides an easy way to do this in the web UI. In the repo's settings, you can change the name of the default branch. |
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.
older repos may still use `master` and should be migrated if possible
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.
I'll leave this for another commit by you or someone else.
|
|
||
| The DSpace@MIT codebase is hosted on Atmire's GitLab organization. In order to add or modify tracking code, you will | ||
| need a GitLab account. As of June 2023, the Digital Library Systems Manager is our point of contact with Atmire. | ||
| The DSpace@MIT codebase is hosted on Atmire's GitLab organization. In order to add or modify tracking code, you will need a GitLab account. As of June 2023, the Digital Library Systems Manager is our point of contact with Atmire. |
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.
I'd mention the position is part of Enterprise Systems as I'd wager people won't know that title. Also, I believe Carl's title is currently Digital Repository Services Engineer
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.
I'm going to leave this for another commit by you or someone else.
These are minor changes in response to the code review for this PR>
Why these changes are being introduced
With the updates to user permissions/privileges/roles in our GitHub Organization, it was time to update our developer documentation to reflect these changes.
How this addresses that need
Side effects of this change
None.