Most of the time forks are used for contributing code only, so not having issues, projects, release and packages is a better default for such cases. They can still be enabled in the settings. A new option `DEFAULT_FORK_REPO_UNITS` is added to configure the default units on forks. Also add missing `repo.packages` unit to documentation. code by: @brechtvl ## ⚠️ BREAKING ⚠️ When forking a repository, the fork will now have issues, projects, releases, packages and wiki disabled. These can be enabled in the repository settings afterwards. To change back to the previous default behavior, configure `DEFAULT_FORK_REPO_UNITS` to be the same value as `DEFAULT_REPO_UNITS`. Co-authored-by: Brecht Van Lommel <brecht@blender.org> |
||
---|---|---|
.. | ||
actions.go | ||
attachment.go | ||
cache.go | ||
cors.go | ||
cron.go | ||
cron_test.go | ||
database.go | ||
database_sqlite.go | ||
database_test.go | ||
directory.go | ||
federation.go | ||
git.go | ||
i18n.go | ||
incoming_email.go | ||
indexer.go | ||
indexer_test.go | ||
lfs.go | ||
log.go | ||
mailer.go | ||
mailer_test.go | ||
markup.go | ||
migrations.go | ||
mime_type_map.go | ||
mirror.go | ||
oauth2_client.go | ||
packages.go | ||
packages_test.go | ||
picture.go | ||
project.go | ||
proxy.go | ||
queue.go | ||
repository.go | ||
service.go | ||
session.go | ||
setting.go | ||
setting_test.go | ||
storage.go | ||
storage_test.go | ||
task.go | ||
webhook.go |