Skip to content
This repository has been archived by the owner on Jan 5, 2024. It is now read-only.

Please, checks after merge #86

Closed
6 tasks
Anton-Latukha opened this issue Nov 12, 2021 · 3 comments
Closed
6 tasks

Please, checks after merge #86

Anton-Latukha opened this issue Nov 12, 2021 · 3 comments
Labels
re: hlint Concerning the hlint actions

Comments

@Anton-Latukha
Copy link
Collaborator

Anton-Latukha commented Nov 12, 2021

There is a number of things that need to be done & checked to make merged hlint actions work properly.

A big diff in #83 thankfully is only haskell/actions/setup specific. There everything is Ok, seems it requires nothing.

Also #82's .github/dependabot.yml is not in #85's Git history. During merge that would resolve itself. Again - that should be no biggy at all. But because I have already redone complex merge several times & then noticed:

hlint-run/.github/dependabot.yml
hlint-setup/.github/dependabot.yml

can not be merged with .github/dependabot.yml in the scope of #85, because the .github/dependabot.yml does not exist there.

After the merge into the mainline - configs of those dependabot.yml files seems need merge into .github. As I found no evidence/docs that localized dependabot configuration would work. Seems like setting according directory: field there would be enough.

  • 2. (optional):

I kept .gitattributes files in according directories. Documentation on gitattributes for me was unclear - does git treats them as it does .gitignore (allowing to place localized .gitignore in any directory. I currently assume, git detects & works with .gitattributes localized just as well.

  • 2. Tags for hlint action versioning need to be made (as GitHub Actions mechanism depends on that) (as the continuations of rwes versioning). & as alpha/beta/pre first.

  • 3. HLint actions (their testing prereleases) need to be published to GitHub Marketplace, so we can test the full actions workflow loop.

  • 4. Final testing

I can test pre-release & then stable release actions on

And on more calm haskell-with-nixpkgs for that matter.

@Anton-Latukha Anton-Latukha changed the title Please, check this after merge Please, checks after merge Nov 12, 2021
@hazelweakly
Copy link
Collaborator

Sweet, this should be working now. One thing to note is that since it's a monorepo, the versioning used by github actions applies uniformly to all of the actions. As such, a breaking change that would require a v2 would mean they're all now v2; due to the nature of these actions (they don't do complicated things), I'm not particularly worried about that, as it shouldn't be difficult to keep the api backwards compatible for them indefinitely.

@Anton-Latukha
Copy link
Collaborator Author

Anton-Latukha commented Jan 6, 2022

I think the merge is comfortable in v1.0 bounds. The old hlint action versioning does not need to be preserved when it essentially changes the name (address).

After I do a couple of things here & there, would do the finishing touches on this merging procedure.

Then the minor dot release would be asked, just to keep old git tag in place & create a new one with the new actions.

@andreasabel
Copy link
Member

andreasabel commented Dec 22, 2022

Not sure why this issue is still open. Closing...

@hazelweakly wrote:

Sweet, this should be working now. One thing to note is that since it's a monorepo, the versioning used by github actions applies uniformly to all of the actions. As such, a breaking change that would require a v2 would mean they're all now v2; due to the nature of these actions (they don't do complicated things), I'm not particularly worried about that, as it shouldn't be difficult to keep the api backwards compatible for them indefinitely.

On that, see:

@andreasabel andreasabel added the re: hlint Concerning the hlint actions label Dec 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
re: hlint Concerning the hlint actions
Projects
None yet
Development

No branches or pull requests

3 participants