Remove archived GWM repository moryoav/ha-gwm_ora

Open Beginner friendly
#5,528 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start by reviewing the HACS default catalogue entry for moryoav/ha-gwm_ora and the related pull request #10742. Done means the archived repository is no longer listed in the default catalogue while the separate current integration submission remains unaffected.

Written by the indexing model from the issue text.

Description

Repository

moryoav/ha-gwm_ora

Checklist
  • I understand that this form should only be used for repositories that needs to be removed from HACS
  • I understand that a bug is not reason enough to have a repository removed
  • The repository is currently shipped as a default repository in HACS
  • I have tried to get the authors attention to the reason for removal

I am the owner and maintainer of this repository, and I am requesting the removal myself.

Why should this be removed?

I have archived the previous GWM repository. The current default integration list still contains moryoav/ha-gwm_ora, which redirects to the archived moryoav/ha-gwm repository.

I continue development in moryoav/ha-gwm-ev. I submitted the current integration separately in https://github.com/hacs/default/pull/10742, with a published release and successful HACS and Hassfest validation.

I originally submitted a one-line replacement, but the HACS bot treated the addition and removal as multiple repository changes. I have changed that PR to add only the new repository and am using this removal form for the archived listing.

My original listing was accepted in https://github.com/hacs/default/pull/8714. Please remove the archived listing from the default catalogue.

Link to issue

https://github.com/hacs/default/pull/10742

This is my related submission as the repository owner. No separate attempt to contact another maintainer is needed because I maintain both repositories.

Dominant language
Python
Stars
7.7k
Forks
1.6k
Avg merge
11h 32m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hacs/integration

All issues in hacs/integration

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.