Update template to use organization actions

[lkdvos]

No description provided.

[lkdvos]

@mtfishman , I think this should be more or less ready, I'll add the updated installation instructions in a separate PR (or do you prefer that here as well)?

Do you know of a reasonable way to tests these actions, apart from just applying this template to one of the packages and checking if everything works? It's a bit annoying for me to do this, since on forked repositories the privileges are actually different from the base ones, so that wouldn't fully reproduce the environment.

[mtfishman]

@mtfishman , I think this should be more or less ready, I'll add the updated installation instructions in a separate PR (or do you prefer that here as well)?

A separate PR for that would be better.

Do you know of a reasonable way to tests these actions, apart from just applying this template to one of the packages and checking if everything works? It's a bit annoying for me to do this, since on forked repositories the privileges are actually different from the base ones, so that wouldn't fully reproduce the environment.

Two ways I came up with were:

1. use the new skeletons to regenerate parts of ITensorPkgSkeleton.jl itself, and
2. generate a package in a temporary repository and check properties of what got generated: https://github.com/ITensor/ITensorPkgSkeleton.jl/blob/main/test/test_basics.jl, for example check that certain files were generated, lines in certain files were generated, etc.

[lkdvos]

Right, but there's no real way to test the github workflows like that right?

[mtfishman]

Right, but there's no real way to test the github workflows like that right?

I guess it checks them implicitly, i.e. you can check parts got generated correctly, and also you can see if the ITensorPkgSkeleton.jl CI runs properly after they are generated from the skeleton.

[lkdvos]

This should now have been done, so this PR is ready from my side.
Closes #11

[mtfishman]

Looks good, thanks!