https://github.com/plugwise/progress
Auto-generates diffs between Core (dev) and Beta (main & branches) to provide an overview what is still to downstream or upstream
https://github.com/plugwise/progress
Last synced: 3 months ago
JSON representation
Auto-generates diffs between Core (dev) and Beta (main & branches) to provide an overview what is still to downstream or upstream
- Host: GitHub
- URL: https://github.com/plugwise/progress
- Owner: plugwise
- Created: 2020-09-08T17:19:27.000Z (almost 6 years ago)
- Default Branch: main
- Last Pushed: 2026-02-01T02:32:20.000Z (4 months ago)
- Last Synced: 2026-02-01T13:40:44.803Z (4 months ago)
- Language: HTML
- Homepage: https://plugwise.github.io/progress/
- Size: 48.6 MB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Plugwise for Home-Assistant Progress
See site details at [Github Plugwise pages](https://plugwise.github.io/progress/)
## How to use?
Any thing we have ready in **our** `home-assistant.core` should be put in `branches.txt`. As we self-use `plugwise-{description}` for PRs add it as such.
As we don't want 'push-by-push', for now (until we make this a PR mandatory repository) you'll have to manually trigger the workflow from [actions](https://github.com/plugwise/progress/actions/workflows/diffy.yml)
## Gotcha's
The github actions on this repo run daily + will self-commit to the repo. As such 'auto'-triggering should be used with care.
Hence the above comment to implement a PR-only trigger (besides the daily one) and not react to 'all' commits.
## PR texts
If you want to prepare a PR text add a `{description}.md` file (as in the description from the core branch `plugwise-{description}`) it will generate a link to that markdown file.