cerc-io/stack-orchestrator
17
1
Fork 3
Code Issues 113 Pull Requests 18 Actions Packages Projects Releases 480 Wiki Activity

Back to Github-based actions. #453

Merged
telackey merged 3 commits from tel/1.20 into main 2023-07-20 02:40:04 +00:00
Conversation 1 Commits 3 Files Changed 4 +5 -5
telackey commented 2023-07-18 20:03:15 +00:00
Member
Copy Link

Update for cf48ed88ba, where actions are pulled from github.com rather than gitea.com

Update for https://gitea.com/gitea/act_runner/commit/cf48ed88ba0400858feb40bffe7ec08ab37ef88b, where actions are pulled from github.com rather than gitea.com
dboreham reviewed 2023-07-18 20:03:15 +00:00
dboreham reviewed 2023-07-18 20:08:54 +00:00
.gitea/workflows/publish.yml
dboreham commented 2023-07-18 20:08:54 +00:00
Owner
Copy Link

This one could be problematic because I had to make code changes in our fork to work with GT. Also that branch isn't present in the GH repo.

This one could be problematic because I had to make code changes in our fork to work with GT. Also that branch isn't present in the GH repo.
telackey reviewed 2023-07-18 20:10:27 +00:00
.gitea/workflows/publish.yml
telackey commented 2023-07-18 20:10:27 +00:00
Author
Member
Copy Link

It seems we could use "self" in that case, but we'd need to migrate the repo to git.vdb.to, because it won't look to an external URL other than Github.

It seems we could use "self" in that case, but we'd need to migrate the repo to git.vdb.to, because it won't look to an external URL other than Github.
telackey reviewed 2023-07-18 20:13:56 +00:00
.gitea/workflows/publish.yml
telackey commented 2023-07-18 20:13:56 +00:00
Author
Member
Copy Link

We might also be able to specify the complete URL explicitly: https://gitea.com/cerc-io/action-gh-release

We might also be able to specify the complete URL explicitly: https://gitea.com/cerc-io/action-gh-release
telackey commented 2023-07-19 21:29:59 +00:00
Author
Member
Copy Link

This works with 1.20, but but would break with 1.19, so we need to coordinate merging this with the upgrade to 1.20.

This works with 1.20, but but would break with 1.19, so we need to coordinate merging this with the upgrade to 1.20.
Sign in to join this conversation.
Reviewers
No reviewers
dboreham
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
feature

   
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
in progress

   
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 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: cerc-io/stack-orchestrator#453
No description provided.
Delete Branch "tel/1.20"

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?