Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

CI goes inactive due to long delays between releases #31

Copy link
Copy link
@alexpeterson91

Description

@alexpeterson91
Issue body actions

I've noticed several updates in the last year were missed or done right in the nick of time because a user or myself found it our nodes offline due to hard forks etc. I just realized yesterday the reason why we werent getting notified was because the CI actions go inactive after a certain amount of time and need to be manually restarted, i did that last night and 4 hours later the CI opened a PR and deployed the test package, @tropicar merged the commit. Im curious is there a way to extend the time before the actions go inactive? we have several smaller not widely used packages like this that have similar issues.

tropicar

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.