README

6.x

Maintainers: Mike Decker, sherakama

Changelog: Changelog.md

Description

This is the main installation profile for Stanford Web Services' self service platform and is used as a base for more.

Accessibility

This module conforms to level AA WCAG 2.0 standards as required by the university's accessibility policy. For more information on the policy please visit: https://ucomm.stanford.edu/policies/accessibility-policy.html.

Installation

Install this installation profile like any other profile. See Drupal Documentation

Upstream updates

Pull from stanford_profile by running the command git pull https://github.com/SU-SWS/stanford_profile.git 12.x -X ours --no-edit.

• If you do not have default pull option configured you will want to add the --no-rebase flag to do a merge commit.

There is possibly going to be some conflicts. Clear up those conflicts and commit the changes.

Releases

Steps to build a new release:

• Checkout the latest commit from the most recent default branch.
• Create a new branch for the release.
• Commit any necessary changes to the release branch.
  • These may include, but are not necessarily limited to:
  • Update the version in any info.yml files, including in any submodules.
  • Update the CHANGELOG to reflect the changes made in the new release.
• Make a PR to merge your release branch into main
• Give the PR a semver-compliant label, e.g., (patch, minor, major). This may happen automatically via Github actions (if a labeler action is configured).
• When the PR is merged to the default branch, a new tag will be created automatically, bumping the version by the semver label.
• The github action is built from: semver-release-action, and further documentation is available there.

Troubleshooting

If you are experiencing issues with this try posting an issue on the GitHub issues page.

Contribution / Collaboration

You are welcome to contribute functionality, bug fixes, or documentation to this module. If you would like to suggest a fix or new functionality you may add a new issue to the GitHub issue queue or you may fork this repository and submit a pull request. For more help please see GitHub's article on fork, branch, and pull requests