I want to create a new GiHub release 1.0.1 of SI Units Checked and Unchecked, but have no idea how.
Please help.
Christoph
I admit, I was a bit terse, excuse me.
I mean: The library has more than 100 library units, some have been modified, some not, some are new, and others have disappeared.
I do not wnat ot update the files one by one.
I do not know what happens to the first release if I delete files.
So the question should have been:
Is there a way to upload a new set of files in one go which leaves the first release untouched and holds only the current files?
Will unchanged files be stored in duplicates?
I could not find a users guide like document.
Disclaimer: I have never done a release in Github
AFAIK, when you do a release, it is like more or less taking a snapshot of your code and creating a git tag. Github treats releases different to git tags as the creator can attach files, or modify a few things. Therefore, when you make a release, you do not have to delete or modify anything. Nevertheless, you could always create a git tag and be sure that things are just going to be fine 
I hope this answers some of your concerns. Here is the official Github documentation about the topic Managing releases in a repository - GitHub Docs
Best regards,
Fer
Frankly, you should probably get a bit more acquainted with how git works. If you treat Github simply as a place for “uploading” files you are probably using it wrong. Instead make full use of its version control capabilities. That way you can “upload” new versions of files (by committing to a local repository and pushing the changes) and still keep the old versions around.
As you are talking about uploading a new snapshot of your sources, the release feature in GitHub won’t help you, as there, you can only tag an existing snapshot (a commit) and upload artifacts (derived files, like executables for various OS or documentation, not sources). On the other hand, the general web interface will only allow you to upload new source files, not to make a full replacement of a copy on which you have worked outside of Git.
As suggested, I think you should try the Git way; it can get complicated, but only for advanced usages. For basic usages, it’s simple.
There are exercises in GitHub that you can follow. It’s not only for the web interface, I think, but for all the workflow. See GitHub - skills-dev/introduction-to-github: Get started using GitHub in less than an hour. There are also Git tutorials in other places, and in fact, you can use just that to work with GitHub, as it will work just as a remote copy of your local repository where you can push your work done locally using just plain Git commands.
Thank you all for your answers, and especially for the link toGitHub Get started.
You’re right, I do not use GitHub in the optimal way. I deem the library nearly perfect, there will at most be bug fixes in the future.
Thus, being old, I’m not interested in the finestructure.
I gather I do know now how to update the repository - when I find the time to - y’know, retirees have a full appointments book ;-).