Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: nutechsoftware/alarmdecoder
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.13.12
Choose a base ref
...
head repository: nutechsoftware/alarmdecoder
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.13.13
Choose a head ref
  • 5 commits
  • 10 files changed
  • 5 contributors

Commits on Feb 23, 2025

  1. Add GitHub Actions workflow for pull requests (#76)

    * Add GitHub Actions workflow for pull requests
    
    This PR adds a GitHub Actions workflow to run `pytest` on pull requests.
    
    This will help ensure no breaking changes are introduced into the
    library.
    
    GitHub Actions is free for public repositories on GitHub.
    
    * try python `3.10`
    ajschmidt8 authored Feb 23, 2025
    Configuration menu
    Copy the full SHA
    c136f94 View commit details
    Browse the repository at this point in the history

Commits on Mar 9, 2025

  1. Configuration menu
    Copy the full SHA
    f930b24 View commit details
    Browse the repository at this point in the history
  2. Be Sure that Expander Zones are Marked as Such (#62)

    A zone can be initially created by an alphanumeric fault message.
    When created this way, the expander attribute is not marked even
    for expander zones.
    
    However, when we receive an expander message, we should update
    the zone attribute to be sure it is identified as an expander.
    
    Co-authored-by: AJ Schmidt <ajs4392@gmail.com>
    krkeegan and ajschmidt8 authored Mar 9, 2025
    Configuration menu
    Copy the full SHA
    389607e View commit details
    Browse the repository at this point in the history
  3. Fix faulted zones clearing iteration logic (#77)

    As provided by warthog618 in #54
    
    The restoration based on message.ready is buggy as it iterates over a list it is deleting from.  which results in only half the faulted zones being cleared.  The fix is to iterate over a copy of the list.
    edrikk authored Mar 9, 2025
    Configuration menu
    Copy the full SHA
    293eed3 View commit details
    Browse the repository at this point in the history
  4. Add automated workflows (#79)

    * commit initial workflows
    
    * get `setup.py` version from `git`
    
    * fix shared action extensions
    
    * fix action paths/names
    
    * run build/test action before release
    
    * set `fetch_tags: true` on `actions/checkout`
    
    * set `fetch_depth: 0` to get all tag history
    
    * revert testing changes for `release.yaml`
    
    * Revert "fix shared action extensions"
    
    This reverts commit 78235c1.
    
    * add docs
    
    * minor doc updates
    ajschmidt8 authored Mar 9, 2025
    Configuration menu
    Copy the full SHA
    ac66ae5 View commit details
    Browse the repository at this point in the history
Loading