mirror of
https://github.com/sdras/awesome-actions.git
synced 2026-07-17 12:02:24 -05:00
Remove deprecated HCL actions? #7
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/awesome-actions#7
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Originally created by @nathany on GitHub (Aug 23, 2019).
I was excited to come across these awesome actions, but it appears that some of the links use the now deprecated HCL syntax-based actions.
Would it make sense to remove or move the actions that use HCL to give emphasize ones that use the current YAML syntax?
Related: https://help.github.com/en/articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax
@gep13 commented on GitHub (Aug 23, 2019):
As per the link that you posted, HCL syntax isn't quite at the deprecated stage yet, but I do agree that we might want to separate, or at least highlight, that a particular action uses a particular format.
Is this something that you would like to take a stab at?
@clarkbw commented on GitHub (Aug 24, 2019):
The Actions should continue to work however the workflow setups won’t and should be updated.
@gep13 commented on GitHub (Aug 24, 2019):
@clarkbw that is good to know! Thank you for confirming that.
@nathany based on this knowledge, I don't see any immediate need to alter the list as it currently stands. Do you?
@sdras commented on GitHub (Aug 25, 2019):
Yeah, I think the list should make mention of this. I'll work on this unless someone else wants to take it.
@gep13 commented on GitHub (Aug 25, 2019):
@sdras that would be great if you could, thank you!
While you are here, can I ask if you saw this: https://github.com/sdras/awesome-actions/issues/95 Thanks!
@DannyBen commented on GitHub (Feb 6, 2020):
For what its worth, I think that even though the HCL syntax is not yet deprecated, it should be considered at least outdated. It had a short shelf-life, and sifting through the list just to find out many things are not relevant, is just adding to the confusion.
I believe the approach to updating this repo should be to separate the HCL to the bottom of the list, or to a separate document, and keep the list clean, focusing exclusively on the new syntax.
@gep13 commented on GitHub (Feb 6, 2020):
@DannyBen did you want to take a stab at doing this?
@DannyBen commented on GitHub (Feb 6, 2020):
I thought @sdras was on the case, no?
@gep13 commented on GitHub (Feb 6, 2020):
That was back in August last year, and since then, the
help wantedlabel has been added, so I am going to say that it is open for contributions.@DannyBen commented on GitHub (Feb 6, 2020):
Ok - I promise to take a look and see if I have the time for it. There are tons of links there, each needs to be carefully reviewed and migrated. No promises, but I might find the time during the weekend.
Do we prefer adding a "(HCL)" (or other) marker neear HCL only items, or do we prefer a completely separate list? The former will probably be easier, since the latter might create weird lists (since they will lose many if not all items).
Edit: I think adding some sort of mark near the ones that are HCL, will probably be the most appropriate first step. Then, we can consider separating the old from the new, either as part of the same edit or as a new PR. Acceptable?
And it seems like HCL is deprecated.
https://github.com/hashicorp/terraform-github-actions/issues/40
I could not find the original comment on the referenced link, I guess it was removed since the deprecation is in effect.