Comments (6)
@rfay thats a good suggestion. Will add more info on the readme. Most people will rather continue using version 1 that's the main reason why I never added that.
from keepalive-workflow.
I don't agree! It's a great new feature, and those commits were a real pain, completely obscuring the history of the repo.
The only thing I don't know is... how do I know it's working? I put a TODO to remember to check one of the repos I changed in 2 months :)
from keepalive-workflow.
Updated this in the changelog as well, Thanks again for the suggestion @rfay
from keepalive-workflow.
I don't doubt it... just wish there was some output or something that gave me confidence.
@rfay it shows output on the test logs, after 50 days of inactivity it will start calling the API.
If you wanna see it calling the API immediately, simply set the time_elapsed
option to 0. Other than that waiting for the next 50 days is the only option for active repositories.
from keepalive-workflow.
Yea, I also agree that commits are a real pain.
The new API based method. As far as I know #1 (comment) suggested that it's working fine. I also tested using some pre-dated commits and it worked just fine.
from keepalive-workflow.
I don't doubt it... just wish there was some output or something that gave me confidence. We'll change https://github.com/ddev/github-action-add-on-test to use v2 and it will affect many, many repositories, and if their tests stop running we may not notice for ages.
Thanks!
from keepalive-workflow.
Related Issues (17)
- Documentation on the impact of a "Dummy commit" HOT 8
- denied by branch protections HOT 1
- "unable to access" issue in multiple projects. HOT 5
- Fails with "Unable to Access" HOT 2
- write permission check using github API HOT 6
- Use branch "keep-alive" HOT 3
- [Question] Write Permission check HOT 4
- Node 20? HOT 1
- Add keepalive using GitHub actions API HOT 2
- Unexpected input(s) 'use_api' during action run HOT 4
- My workflow has been disabled even if I use this action HOT 2
- Workflow being disabled even though v2 is in use HOT 9
- Extraneous parameters reported in v2 HOT 1
- Action does not complete and causes the parent workflow to fail. (triggered by pull request from fork) HOT 2
- run failed HOT 1
- Error when using workflow HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from keepalive-workflow.