Thank you for contributing to the Data Science for OpenWashData course website!
- Maintainer: @larnsce - Reviews and merges PRs from
devtomain - Contributors: @massarin, @seawaR - Create feature branches and submit PRs to
dev
We follow a structured Git workflow to maintain code quality:
- Main branch (
main): Production-ready code, deployed to GitHub Pages - Development branch (
dev): Integration branch for all features - Feature branches: Individual contributions from
dev
-
Create a feature branch from
dev:git checkout dev git pull origin dev git checkout -b feature-name
-
Make your changes and commit regularly:
git add . git commit -m "Description of changes"
-
Push your feature branch:
git push origin feature-name
-
Open a Pull Request:
- Create PR from your feature branch →
dev - Use GitHub CLI:
gh pr create --base dev --title "Your PR title" - @larnsce will review and approve the PR
- Create PR from your feature branch →
-
Share PR link in Element Chat communication channel for team visibility
-
After approval: @larnsce merges the PR into
dev -
Deployment: @larnsce periodically merges
dev→mainfor production releases
This project uses renv for reproducible R package management.
# Install renv if needed
install.packages("renv")
# Restore project dependencies
renv::restore()When you need a new R package:
# Install the package
install.packages("package_name")
# Update the lockfile
renv::snapshot()
# Commit the updated renv.lock file
git add renv.lock
git commit -m "Add package_name dependency"# Update specific package
renv::update("package_name")
# Update all packages
renv::update()
# Commit changes
git add renv.lock
git commit -m "Update R package dependencies"If you encounter package issues:
# Check project status
renv::status()
# Restore from lockfile
renv::restore()
# Clean and rebuild
renv::clean()
renv::restore()- Element Chat: Share PR links and coordinate work
- GitHub Issues: Track bugs and feature requests
- PR Comments: Technical discussion about specific changes
If you have questions about contributing, reach out to @larnsce or ask in the Element Chat channel.