You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
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:
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
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.
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.
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.
There is a number of things that need to be done & checked to make merged
hlint
actions work properly.haskell/actions
main fork branch to recent commits, that is - after add dependabot: add Actions CI merge requests automation #82 & Fixes for linking errors on 7.10.3 and cleaning up symlinks #83 got merged.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: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 localizeddependabot
configuration would work. Seems like setting accordingdirectory:
field there would be enough.I kept
.gitattributes
files in according directories. Documentation ongitattributes
for me was unclear - doesgit
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
rwe
s versioning). & asalpha/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.
5. Closes:
The text was updated successfully, but these errors were encountered: