-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Transition To Workbench in May #336
Comments
This lesson will be converted to use The Carpentries Workbench
If you no longer wish to have write access to this repository, you do not
If you wish to regain write access, please re-clone the repository on your machine and If you have any questions, please reply here and tag @zkamvar |
The deed is done. The infrastructure takes a few minutes to bootstrap and cache the packages for the lesson build. Once the build is done, I will switch github pages to deploy from the Thank you all for your enthusiasm and your patience! |
The Workbench version is now live: https://datacarpentry.github.io/shell-genomics/ In addition, here is map of commits that were changed during the transition |
Hi @zkamvar, I am ready for write access 🚀 Cheers, |
@vhmcck creating a new fork is definitely helpful here. Local clones should be replaced too. The transition to the Workbench modified the history of the project, removing the commits that were associated with changes to the lesson site infrastructure to leave only those changes that are relevant to the content of the lesson itself. Anyone with an existing fork or clone of the pre-Workbench version of the lesson has a default branch that still includes all of those infrastructure-only commits. This means they could open a pull request that would introduce the old history back into the project - a change which, if merged, would be complicated to undo. Maintainers have the power to merge their own pull requests to the lesson, so the easiest way to be confident that the old project history will not be merged back into the lesson is for those Maintainers to delete and replace any copies of the repository that they have access to e.g. forks and local clones. I hope that answers your question - please feel free to ask if you would like more details or if anything is unclear in my explanation. |
@vhmcck access granted! What @tobyhodges said should be the gist of it. I will add that if you've only ever worked directly in GitHub (e.g. you always work on your repository in your web browser and never had to use |
Thank you so much @tobyhodges, @zkamvar ! |
Hi, I've deleted my clones and I'm ready for write access 🚀 |
Thank you for responding, @p-j-smith! Access granted! Congratulations, all the maintainers of this lesson now have access! |
thank you @zkamvar ! |
@datacarpentry/shell-genomics-maintainers
As I hope you are already aware, we are rolling out the new lesson infrastructure, The Carpentries Workbench, across all of The Carpentries official lessons in early May 2023. This means that all Data Carpentry, Library Carpentry, and Software Carpentry lesson repositories will be modified to adopt the new infrastructure in the coming days.
You can follow the transition of this lesson repository at carpentries/lesson-transition#42.
The transition has already taken place for several lessons, and so far the process has been running quite smoothly. You should see the transition take place with minimal disruption, but there are a few things that it is important for Maintainers to be aware of.
Here is what you can expect to happen next:
I will reply here before and after the transition has taken place. If you have any questions in the meantime, please reach out to the Curriculum Team by tagging us here, e.g. @datacarpentry/core-team-curriculum.
If you would like to read more about the new lesson infrastructure and the modified repository structure you can expect post-transition, I recommend the Infrastructure episode of the Maintainer Onboarding curriculum and the Workbench Transition Guide, which includes a side-by-side comparison of various elements of the old and new infrastructures.
The text was updated successfully, but these errors were encountered: