Can repository informations be provided via environment variables?

[sroertgen]

No description provided.

[sroertgen]

https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables

[sroertgen]

@acka47 I merged this into main.

Feel free to test.

Consider the following scenarios:

• someone forks this repo with the same name and modifies some vocabularies.
• someone changes the name of the repo when forking and modifies some vocabularies.

Both cases should work.

We use this issue to discuss further and will close it when everything is ok.

[acka47]

This looks really nice. I have tested it.

someone forks this repo with the same name and modifies some vocabularies.

I have checked this and it works.

someone changes the name of the repo when forking and modifies some vocabularies.

I also did that and it works, see https://github.com/acka47test/test-vocabs

However, with each test, I ran into some problems and it did not work directly (which was my fault).

I suggest the following:

• Shorten the "Usage" list, especially bullet point 3 with the steps you have to follow to make everything work directly.
• Add a troubleshooting paragraph where the most common problems (gh-pages not forked, branch not set for pages, Actions not activated) are adressed.
• We should also think about adding screenshots to the usage paragraph.

[sroertgen]

I shortened the usage section and added a troubleshooting section.

Regarding screenshots I'm hesitating since they blow up the size of the git repo.
Maybe we should put them somewhere different (like a tutorials repository) and just link them from there?

[acka47]

I shortened the usage section and added a troubleshooting section.

This is much better. I tried to make it even a bit more concise with #23 .

Regarding screenshots I'm hesitating since they blow up the size of the git repo.
Maybe we should put them somewhere different (like a tutorials repository) and just link them from there?

I agree, this make sense and we already discussed this approach yesterday, see skohub-io/skohub.io#19 (comment)

[sroertgen]

@acka47 so then I will close this now and I will make a new issue to add screenshots to the usage section. ok?

[acka47]

so then I will close this now and I will make a new issue to add screenshots to the usage section. ok?

I think, we should just keep this in mind for implementing skohub-io/skohub.io#19 (which will be done in a different repo than this, I think).

[acka47]

I think, we should just keep this in mind for implementing skohub-io/skohub.io#19 (which will be done in a different repo than this, I think).

I've added it in skohub-io/skohub.io#19 (comment), feel free to close this one now.