The GitHub MarkDown renderer doesn't support either of the two protocols, so no interactive links in your MarkDown files.
The target
attribute is not supported in links made using the a
tag.
GitHub won't check the submodule out upon just creation of .gitmodules
.
A Git client needs to be used to checkout the submodule and push to the remote
so that the submodule files at the given hash appear as a submodule directory
in the GitHub web UI.
When a repository contains a submodule, that submodule appears as a subdirectory in a GitHub Pages website.
Of course to update its contents the submodule needs to be updated through a Git client as GitHub web UI doesn't have a control for updating submodules.
This is also useless for Service Workers because the scope is given by the submodule directory and cannot intercept requests of the web app at the root directory path.
GitLab Enterprise has a paid built-in feature for 2-way synchonization: Repository mirroring
Tomas Wood made a tool which uses APIs and hooks to cross-synchonize repositories.
Steve Perkins documented two approaches:
- Named remotes
- Overloaded
origin
Of course neither will synchronize non-Git objects, such as PRs and issues.
GitHub will render SVG files in the readme and even play CSS animations in them.
- There is
stargazers_count
andwatchers_count
on the repository model and both are the same thing! The actual watchers are insubscribers_count
- An individual repo's details will contain its watcher count, but the get-repos
endpoint will not return the
subscribers_count
field - The
open_issues_count
field on the repository model combines the number of open issues and the number of open pull requests and there is no way to tell the two apart just based on that model - The Activity API (events) does not have the right
payload.action
values or even correct payload fields as documented: https://github.com/TomasHubelbauer/tomashubelbauer/blob/main/index.js