-
-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
Open
13 tasks
Tracked by
#5644
roslynwythe opened this issue
Feb 8, 2024
· 23 comments
· May be fixed by danielridgebot/check-ghpages-versions#21
Open
13 tasks
Tracked by
#5644
Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated #6266
roslynwythe opened this issue
Feb 8, 2024
· 23 comments
· May be fixed by danielridgebot/check-ghpages-versions#21
Labels
Complexity: Large
Feature: Docker
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
size: 2pt
Can be done in 7-12 hours
Milestone
Comments
roslynwythe
added
role: back end/devOps
Tasks for back-end developers
Complexity: Medium
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
size: missing
size: 1pt
Can be done in 4-6 hours
Draft
Issue is still in the process of being created
Feature: Docker
role missing
Complexity: Missing
labels
Feb 8, 2024
github-actions
bot
removed
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
size: missing
role missing
Complexity: Missing
labels
Feb 8, 2024
roslynwythe
added
ready for product
and removed
Draft
Issue is still in the process of being created
labels
Feb 8, 2024
This comment was marked as outdated.
This comment was marked as outdated.
6 tasks
This comment was marked as outdated.
This comment was marked as outdated.
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
ready for product
labels
Feb 11, 2024
ExperimentsInHonesty
added
the
time sensitive
Needs to be worked on by a particular timeframe
label
Feb 13, 2024
roslynwythe
added
Ready for Prioritization
and removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Feb 25, 2024
This comment was marked as outdated.
This comment was marked as outdated.
2 tasks
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
Ready for Prioritization
labels
Feb 25, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This was referenced Jun 6, 2024
roslynwythe
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
ready for merge team
needs a senior review either to do some re writing or to approve it for ready for prioritization
labels
Jun 14, 2024
ExperimentsInHonesty
moved this to Questions / In Review
in P: HfLA Website: Project Board
Jun 23, 2024
t-will-gillis
moved this from Questions / In Review
to New Issue Approval
in P: HfLA Website: Project Board
Jun 30, 2024
ExperimentsInHonesty
moved this from New Issue Approval
to Questions / In Review
in P: HfLA Website: Project Board
Jul 2, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
github-actions
bot
added
the
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
label
Aug 2, 2024
This comment was marked as outdated.
This comment was marked as outdated.
ExperimentsInHonesty
removed
the
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
label
Sep 24, 2024
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
removed
time sensitive
Needs to be worked on by a particular timeframe
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Nov 3, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
ExperimentsInHonesty
moved this from Questions / In Review
to New Issue Approval
in P: HfLA Website: Project Board
Nov 5, 2024
ExperimentsInHonesty
added
Draft
Issue is still in the process of being created
and removed
Added to dev/pm agenda
labels
Nov 5, 2024
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
added
Ready for Prioritization
and removed
Draft
Issue is still in the process of being created
labels
Nov 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Complexity: Large
Feature: Docker
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
size: 2pt
Can be done in 7-12 hours
Overview
We need to implement a "Keepalive Workflow" for the Daniel Ridge bot so that it performs its function of checking the dependencies for the Docker image and when necessary, updating the Dockerfile, which triggers the process of updating our Docker hub image.
Details
Action Items
How To Use section of the Keep-Alive Workflow documentation
.github/workflows/check-ruby-version.yml
.github/workflows/check-gh-pages-version.yml
check-gh-pages-version,yml
explaning the addition of the KeepAlive Workflow action.github/workflows/check-gh-pages-version.yml
and verify that the appropriate issues were createdResources/Instructions
check-gh-pages-version.yml
Keep Alive Workflow
How To Use section of the Keep-Alive Workflow documentation
The text was updated successfully, but these errors were encountered: