https://github.com/su-sws/stanford_date_formats
Date and time formats used by Stanford modules and Themes
https://github.com/su-sws/stanford_date_formats
d7 d8 module
Last synced: 6 months ago
JSON representation
Date and time formats used by Stanford modules and Themes
- Host: GitHub
- URL: https://github.com/su-sws/stanford_date_formats
- Owner: SU-SWS
- License: gpl-2.0
- Created: 2012-11-26T23:40:39.000Z (over 13 years ago)
- Default Branch: 8.x
- Last Pushed: 2022-07-08T20:31:14.000Z (about 4 years ago)
- Last Synced: 2025-06-24T08:09:28.769Z (about 1 year ago)
- Topics: d7, d8, module
- Size: 39.1 KB
- Stars: 1
- Watchers: 31
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# [Stanford Date Formats](https://github.com/SU-SWS/stanford_date_formats)
##### Version: 8.x
[](https://circleci.com/gh/SU-SWS/stanford_date_formats)
Maintainers: [jbickar](https://github.com/jbickar), [sherakama](https://github.com/sherakama)
[Changelog.txt](CHANGELOG.txt)
This feature contains several date formats for use with other features and custom work. This is more of a utility feature and does not do much on its own.
Installation
---
Install this module like any other module. [See Drupal Documentation](https://drupal.org/documentation/install/modules-themes/modules-7)
Configuration
---
Nothing special needed.
Troubleshooting
---
If you are experiencing issues with this module try reverting the feature first. If you are still experiencing issues 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](https://help.github.com/articles/using-pull-requests)
Releases
---
Steps to build a new release:
- Checkout the latest commit from the `8.x-1.x` 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 `master`
- 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 `master`, a new tag will be created automatically, bumping the version by the semver label.
- The github action is built from: [semver-release-action](https://github.com/K-Phoen/semver-release-action), and further documentation is available there.