Skip to content

Use GitHub project for contributor lists instead of a file #4182

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 12, 2024
Merged

Use GitHub project for contributor lists instead of a file #4182

merged 1 commit into from
Nov 12, 2024

Conversation

lornajane
Copy link
Contributor

Fixes #4148 by removing the file.

@lornajane lornajane requested review from a team as code owners November 8, 2024 15:29
@ralfhandl
Copy link
Contributor

ralfhandl commented Nov 11, 2024 •
edited
Loading

@handrews Will dev, v3.1-dev, and v3.2-dev be updated from main after merging this?

@handrews
Copy link
Member

@ralfhandl up to the TSC. I definitely do not want to be the person in charge of approving every branch/merge step.

@ralfhandl ralfhandl mentioned this pull request Nov 12, 2024
Closed
@ralfhandl ralfhandl merged commit fdbaebf into OAI:main Nov 12, 2024
2 checks passed
@lornajane
Copy link
Contributor Author

Yes, we'll merge main into those dev branches on an informal schedule - I suggest we work through more of these docs updates and then do some dev branch updates to keep everyone aligned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ralfhandl ralfhandl ralfhandl approved these changes

@handrews handrews handrews approved these changes

Assignees
No one assigned
Labels
Housekeeping
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Remove/replace/migrate the CONTRIBTORS file
3 participants
@lornajane @ralfhandl @handrews