Hithomelabs/CFTunnels
5
0
Fork 3
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merging to main #90

Merged
hitanshu merged 12 commits from test into main 2025-11-14 20:09:57 +00:00
Conversation 0 Commits 12 Files Changed 8 +136 -16
hitanshu commented 2025-11-14 20:08:17 +00:00
Owner
Copy Link
No description provided.
hitanshu self-assigned this 2025-11-14 20:08:17 +00:00
hitanshu added 12 commits 2025-11-14 20:08:17 +00:00
[Added a script for auto syncing forks of parent repository] Beta #1
All checks were successful
sample gradle build and test / build (pull_request) Successful in 2m10s
Details
665361a4e3
[Added a script for auto syncing forks of parent repository] Beta #2
All checks were successful
sample gradle build and test / build (pull_request) Successful in 1m45s
Details
sample gradle build and test / tag (push) Successful in 6s
Details
sample gradle build and test / build_tag_push (push) Successful in 2m21s
Details
sample gradle build and test / Sync All Forks (push) Successful in 8s
Details
ef7b6545db
[Added a script for auto syncing forks of parent repository] Beta #3
All checks were successful
sample gradle build and test / build (pull_request) Successful in 2m17s
Details
sample gradle build and test / build_tag_push (push) Successful in 2m22s
Details
sample gradle build and test / tag (push) Successful in 7s
Details
sample gradle build and test / Sync All Forks (push) Successful in 8s
Details
46e8f614a0
ISSUE-44: Hithomelabs/HomeLabDocker#44 Minor bug fix
Some checks failed
sample gradle build and test / build (pull_request) Failing after 2m29s
Details
8039945f2a
ISSUE-44: Hithomelabs/HomeLabDocker#44 Reducing logging verbiage, excuding integration test from test profile
Some checks failed
sample gradle build and test / build (pull_request) Failing after 2m6s
Details
b2d58d6a61
ISSUE-44: Hithomelabs/HomeLabDocker#44 Excluding integration tests from gradle build and runs them separately in integration tests
All checks were successful
sample gradle build and test / build (pull_request) Successful in 2m11s
Details
e87fb6d153
Merge pull request 'ISSUE-44: Adding integration tests and setting up workflow' (#88) from hitanshu/CFTunnels:ISSUE-44 into test
All checks were successful
sample gradle build and test / tag (push) Successful in 7s
Details
sample gradle build and test / build_tag_push (push) Successful in 2m54s
Details
sample gradle build and test / Sync All Forks (push) Successful in 12s
Details
Daily cloudflare API integration test / cloudflare-api-test (push) Successful in 1m27s
Details
f7e4b3fd93 
Reviewed-on: #88
ISSUE-44: Hithomelabs/HomeLabDocker#44 making tests more verbose
All checks were successful
sample gradle build and test / tag (push) Successful in 6s
Details
sample gradle build and test / build_tag_push (push) Successful in 2m4s
Details
sample gradle build and test / Sync All Forks (push) Successful in 11s
Details
Promote image with tag test to prod / tag (push) Successful in 7s
Details
Promote image with tag test to prod / build_tag_push (push) Successful in 14s
Details
Daily cloudflare API integration test / cloudflare-api-test (push) Successful in 1m33s
Details
f36d807731
hitanshu requested review from kruti 2025-11-14 20:08:39 +00:00
hitanshu merged commit f36d807731 into main 2025-11-14 20:09:57 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
kruti
Labels
Clear labels
  
epic
analytics
Data analytics of platform data and logs analysis.

  
epic
development
Developing new features, services. front and and back end as well as batch jobs

  
epic
devops
Epic related to CI/CD pipeline, runners, setup and workflow triggers

  
epic
infra
Epic related to infrastructure tasks, configuring hard drives, network equipment, firewalls, anything involving getting hands dirty.

  
epic
observability
Observability stack, uptime, service discovery, network, firewall, processes, resource consumption etc.

  
epic
platform
Related to authentication, authorization, keys, passwords, configs. Updates and upgrades related to platform.

  
epic
product
Issues discussing products and features come over here.

  
priority
later
To be done but can wait. Generally areas that don't want immediate attention and warrant pre-planning, analysis and/or design

  
priority
next
Not a burning issue but needs to be worked on next. Generally should not be blocked by any issue other than priority::now

  
priority
now
Immediate priority, critical for PROD go-live

  
status
acceptance
Testing results are good and issue looks good to deploy. It is a pre-deployment sign-off of test results

  
status
blocked
Need to solve another issue before this issue can be picked. The issue is blocked till the blocking issue isn't resolved

  
status
done
Issue deployment successful.

  
status
in progress
Issue has been picked up and someone is working on it.

  
status
in review
The issue has been work on but, a review has been requested, generally good to transition to this if all PRs raised require review or are reviewed.

  
status
in testing
Code review complete and issue is in testing in lower environment. P.S. This means unit tests have already been written.

  
status
ready
Issue does not have any blocker and is ready to be picked.

  
status
refine
Something working already well in PROD but a change that makes life a little more easier, like skip into in netflix. Issues that signify added convenience.

  
status
triage
Issue is requested but not scoped. Need to be added to systematically review and categorize

  
type
analysis
An issue to perform analysis, exploring deign and implementation decisions/ considerations.

  
type
bug
A bug, needs to be fixed, raised out of an incident.

  
type
hygiene
Features remain the same, makes the platform, faster, better and less-error prone. Makes developer/ system-admin life easier

  
type
mantainence
Primarily version upgrades

  
type
story
Something new, a new feature !

No Label
epic
analytics
epic
development
epic
devops
epic
infra
epic
observability
epic
platform
epic
product
priority
later
priority
next
priority
now
status
acceptance
status
blocked
status
done
status
in progress
status
in review
status
in testing
status
ready
status
refine
status
triage
type
analysis
type
bug
type
hygiene
type
mantainence
type
story
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
hitanshu
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hithomelabs/CFTunnels#90
No description provided.
Delete Branch "test"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?