Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CI #2

Open
ben-grande opened this issue Sep 22, 2024 · 3 comments
Open

Add CI #2

ben-grande opened this issue Sep 22, 2024 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@ben-grande
Copy link
Owner

Qusal has a lot of checks done by Github Actions. The problem is how to make it reusable (avoid code duplication).

The Github Action reusability is easy, but the problem is the qusal/scripts directory, how to reuse it? If it is not possible, how to keep it in sync? Prohibit changes to it from downstream dotfiles and only allow changes to be made directly to qusal and then copied to dotfiles?

Impacts:

@ben-grande ben-grande added enhancement New feature or request help wanted Extra attention is needed labels Sep 22, 2024
@seven-beep
Copy link

You seems very well versed in good practices, so take my comment with a grain of salt,

What is the plus value of making this repository a submodule ? Do you use it as standalone ? It does not seems so ...

I understand that by principle you want to separate your 'dotfiles' from 'qusal' from a theorical perspective but well ...

At this point, 'dotfiles' is not a personal configuration but a needed dependency for 'qusal'.

Why not merging it into qusal ? The benefits would be :

  • No more issues about github actions
  • less instructions to setup qusal from git

@ben-grande
Copy link
Owner Author

You seems very well versed in good practices, so take my comment with a grain of salt,

I try, but not sure, this is my first big project.

What is the plus value of making this repository a submodule ? Do you use it as standalone ? It does not seems so ...

So it can be used outside of Qubes environment without having extra unneeded files involved, as the dotfiles are not Qubes specific, although they have specific Qubes files.

I use it as a standalone when I install my dotfiles to any machine, but I guess that if problems arise of not having CI, I may sacrifice it for a way to fix the bigger problem.

I understand that by principle you want to separate your 'dotfiles' from 'qusal' from a theorical perspective but well ...

The dotfiles were actually a directory just like any other formula, but you can't see that through commit as this was before I had a clean history and the first commit already has dotfiles as a submodule.

At this point, 'dotfiles' is not a personal configuration but a needed dependency for 'qusal'.

I try to not make my dotfiles a personal configuration, allowing for user configuration, but I understand your point. It is true that at this stage, before implementing the dotfiles' pillars, it is a dependency, that I'm hoping it won't be anymore.

Why not merging it into qusal ? The benefits would be :

  • No more issues about github actions
  • less instructions to setup qusal from git

That is true, submodules really lengthen up the instructions. I will think about that, I will study more in the meantime.

When I moved dotfiles to its own submodule, I did not think through of these consequences, I guess only time can teach.

@seven-beep
Copy link

use it as a standalone when I install my dotfiles to any machine, but I guess that if problems arise of not having CI, I may sacrifice it for a way to fix the bigger problem.

This is very a solid reason, indeed.

Looking at the community discussions, peoples seem to workaround this by using a docker image to embed the necessary files or to fetch the raw files rather than using their path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants