Show messages for users if the ROOT_URL is wrong, show JavaScript errors (#18971)
* ROOT_URL issues: some users did wrong to there app.ini config, then:
* The assets can not be loaded (AppSubUrl != "" and users try to access http://host:3000/)
*The ROOT_URL is wrong, then many URLs in Gitea are broken.
Now Gitea show enough information to users.
* JavaScript error issues, there are many users affected by JavaScript errors, some are caused by frontend bugs, some are caused by broken customized templates. If these JS errors can be found at first time, then maintainers do not need to ask about how bug occurs again and again.
* Some people like to modify the `head.tmpl`, so we separate the script part to `head_script.tmpl`, then it's much safer.
* use specialized CSS class "js-global-error", end users still have a chance to hide error messages by customized CSS styles.
3 years ago
// bootstrap module must be the first one to be imported, it handles webpack lazy-loading and global errors
import './bootstrap.ts' ;
import './htmx.ts' ;
import { initRepoActivityTopAuthorsChart } from './components/RepoActivityTopAuthors.vue' ;
import { initDashboardRepoList } from './components/DashboardRepoList.vue' ;
import { initGlobalCopyToClipboardListener } from './features/clipboard.ts' ;
import { initContextPopups } from './features/contextpopup.ts' ;
import { initRepoGraphGit } from './features/repo-graph.ts' ;
import { initHeatmap } from './features/heatmap.ts' ;
import { initImageDiff } from './features/imagediff.ts' ;
import { initRepoMigration } from './features/repo-migration.ts' ;
import { initRepoProject } from './features/repo-projects.ts' ;
import { initTableSort } from './features/tablesort.ts' ;
import { initAutoFocusEnd } from './features/autofocus-end.ts' ;
import { initAdminUserListSearchForm } from './features/admin/users.ts' ;
import { initAdminConfigs } from './features/admin/config.ts' ;
import { initMarkupAnchors } from './markup/anchors.ts' ;
import { initNotificationCount , initNotificationsTable } from './features/notification.ts' ;
import { initRepoIssueContentHistory } from './features/repo-issue-content.ts' ;
import { initStopwatch } from './features/stopwatch.ts' ;
import { initFindFileInRepo } from './features/repo-findfile.ts' ;
import { initCommentContent , initMarkupContent } from './markup/content.ts' ;
import { initPdfViewer } from './render/pdf.ts' ;
import { initUserAuthOauth2 } from './features/user-auth.ts' ;
import {
initRepoIssueDue ,
initRepoIssueReferenceRepositorySearch ,
initRepoIssueTimeTracking ,
initRepoIssueWipTitle ,
initRepoPullRequestMergeInstruction ,
initRepoPullRequestAllowMaintainerEdit ,
initRepoPullRequestReview , initRepoIssueSidebarList , initArchivedLabelHandler ,
} from './features/repo-issue.ts' ;
import { initRepoEllipsisButton , initCommitStatuses } from './features/repo-commit.ts' ;
import { initRepoTopicBar } from './features/repo-home.ts' ;
import { initAdminEmails } from './features/admin/emails.ts' ;
import { initAdminCommon } from './features/admin/common.ts' ;
import { initRepoTemplateSearch } from './features/repo-template.ts' ;
import { initRepoCodeView } from './features/repo-code.ts' ;
import { initSshKeyFormParser } from './features/sshkey-helper.ts' ;
import { initUserSettings } from './features/user-settings.ts' ;
import { initRepoArchiveLinks } from './features/repo-common.ts' ;
import { initRepoMigrationStatusChecker } from './features/repo-migrate.ts' ;
import {
initRepoSettingGitHook ,
initRepoSettingsCollaboration ,
initRepoSettingSearchTeamBox ,
} from './features/repo-settings.ts' ;
import { initRepoDiffView } from './features/repo-diff.ts' ;
import { initOrgTeamSearchRepoBox , initOrgTeamSettings } from './features/org-team.ts' ;
import { initUserAuthWebAuthn , initUserAuthWebAuthnRegister } from './features/user-auth-webauthn.ts' ;
import { initRepoRelease , initRepoReleaseNew } from './features/repo-release.ts' ;
import { initRepoEditor } from './features/repo-editor.ts' ;
import { initCompSearchUserBox } from './features/comp/SearchUserBox.ts' ;
import { initInstall } from './features/install.ts' ;
import { initCompWebHookEditor } from './features/comp/WebHookEditor.ts' ;
import { initRepoBranchButton } from './features/repo-branch.ts' ;
import { initCommonOrganization } from './features/common-organization.ts' ;
import { initRepoWikiForm } from './features/repo-wiki.ts' ;
Actions support workflow dispatch event (#28163)
fix #23668
My plan:
* In the `actions.list` method, if workflow is selected and IsAdmin,
check whether the on event contains `workflow_dispatch`. If so, display
a `Run workflow` button to allow the user to manually trigger the run.
* Providing a form that allows users to select target brach or tag, and
these parameters can be configured in yaml
* Simple form validation, `required` input cannot be empty
* Add a route `/actions/run`, and an `actions.Run` method to handle
* Add `WorkflowDispatchPayload` struct to pass the Webhook event payload
to the runner when triggered, this payload carries the `inputs` values
and other fields, doc: [workflow_dispatch
payload](https://docs.github.com/en/webhooks/webhook-events-and-payloads#workflow_dispatch)
Other PRs
* the `Workflow.WorkflowDispatchConfig()` method still return non-nil
when workflow_dispatch is not defined. I submitted a PR
https://gitea.com/gitea/act/pulls/85 to fix it. Still waiting for them
to process.
Behavior should be same with github, but may cause confusion. Here's a
quick reminder.
*
[Doc](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)
Said: This event will `only` trigger a workflow run if the workflow file
is `on the default branch`.
* If the workflow yaml file only exists in a non-default branch, it
cannot be triggered. (It will not even show up in the workflow list)
* If the same workflow yaml file exists in each branch at the same time,
the version of the default branch is used. Even if `Use workflow from`
selects another branch
![image](https://github.com/go-gitea/gitea/assets/3114995/4bf596f3-426b-48e8-9b8f-0f6d18defd79)
```yaml
name: Docker Image CI
on:
workflow_dispatch:
inputs:
logLevel:
description: 'Log level'
required: true
default: 'warning'
type: choice
options:
- info
- warning
- debug
tags:
description: 'Test scenario tags'
required: false
type: boolean
boolean_default_true:
description: 'Test scenario tags'
required: true
type: boolean
default: true
boolean_default_false:
description: 'Test scenario tags'
required: false
type: boolean
default: false
environment:
description: 'Environment to run tests against'
type: environment
required: true
default: 'environment values'
number_required_1:
description: 'number '
type: number
required: true
default: '100'
number_required_2:
description: 'number'
type: number
required: true
default: '100'
number_required_3:
description: 'number'
type: number
required: true
default: '100'
number_1:
description: 'number'
type: number
required: false
number_2:
description: 'number'
type: number
required: false
number_3:
description: 'number'
type: number
required: false
env:
inputs_logLevel: ${{ inputs.logLevel }}
inputs_tags: ${{ inputs.tags }}
inputs_boolean_default_true: ${{ inputs.boolean_default_true }}
inputs_boolean_default_false: ${{ inputs.boolean_default_false }}
inputs_environment: ${{ inputs.environment }}
inputs_number_1: ${{ inputs.number_1 }}
inputs_number_2: ${{ inputs.number_2 }}
inputs_number_3: ${{ inputs.number_3 }}
inputs_number_required_1: ${{ inputs.number_required_1 }}
inputs_number_required_2: ${{ inputs.number_required_2 }}
inputs_number_required_3: ${{ inputs.number_required_3 }}
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- run: ls -la
- run: env | grep inputs
- run: echo ${{ inputs.logLevel }}
- run: echo ${{ inputs.boolean_default_false }}
```
![image](https://github.com/go-gitea/gitea/assets/3114995/a58a842d-a0ff-4618-bc6d-83a9596d07c8)
![image](https://github.com/go-gitea/gitea/assets/3114995/44a7cca5-7bd4-42a9-8723-91751a501c88)
---------
Co-authored-by: TKaxv_7S <954067342@qq.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Denys Konovalov <kontakt@denyskon.de>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
3 months ago
import { initRepoCommentForm , initRepository , initBranchSelectorTabs } from './features/repo-legacy.ts' ;
import { initCopyContent } from './features/copycontent.ts' ;
import { initCaptcha } from './features/captcha.ts' ;
Implement actions (#21937)
Close #13539.
Co-authored by: @lunny @appleboy @fuxiaohei and others.
Related projects:
- https://gitea.com/gitea/actions-proto-def
- https://gitea.com/gitea/actions-proto-go
- https://gitea.com/gitea/act
- https://gitea.com/gitea/act_runner
### Summary
The target of this PR is to bring a basic implementation of "Actions",
an internal CI/CD system of Gitea. That means even though it has been
merged, the state of the feature is **EXPERIMENTAL**, and please note
that:
- It is disabled by default;
- It shouldn't be used in a production environment currently;
- It shouldn't be used in a public Gitea instance currently;
- Breaking changes may be made before it's stable.
**Please comment on #13539 if you have any different product design
ideas**, all decisions reached there will be adopted here. But in this
PR, we don't talk about **naming, feature-creep or alternatives**.
### ⚠️ Breaking
`gitea-actions` will become a reserved user name. If a user with the
name already exists in the database, it is recommended to rename it.
### Some important reviews
- What is `DEFAULT_ACTIONS_URL` in `app.ini` for?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1055954954
- Why the api for runners is not under the normal `/api/v1` prefix?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061173592
- Why DBFS?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1061301178
- Why ignore events triggered by `gitea-actions` bot?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1063254103
- Why there's no permission control for actions?
- https://github.com/go-gitea/gitea/pull/21937#discussion_r1090229868
### What it looks like
<details>
#### Manage runners
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205870657-c72f590e-2e08-4cd4-be7f-2e0abb299bbf.png">
#### List runs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872794-50fde990-2b45-48c1-a178-908e4ec5b627.png">
#### View logs
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205872501-9b7b9000-9542-4991-8f55-18ccdada77c3.png">
</details>
### How to try it
<details>
#### 1. Start Gitea
Clone this branch and [install from
source](https://docs.gitea.io/en-us/install-from-source).
Add additional configurations in `app.ini` to enable Actions:
```ini
[actions]
ENABLED = true
```
Start it.
If all is well, you'll see the management page of runners:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205877365-8e30a780-9b10-4154-b3e8-ee6c3cb35a59.png">
#### 2. Start runner
Clone the [act_runner](https://gitea.com/gitea/act_runner), and follow
the
[README](https://gitea.com/gitea/act_runner/src/branch/main/README.md)
to start it.
If all is well, you'll see a new runner has been added:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205878000-216f5937-e696-470d-b66c-8473987d91c3.png">
#### 3. Enable actions for a repo
Create a new repo or open an existing one, check the `Actions` checkbox
in settings and submit.
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879705-53e09208-73c0-4b3e-a123-2dcf9aba4b9c.png">
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205879383-23f3d08f-1a85-41dd-a8b3-54e2ee6453e8.png">
If all is well, you'll see a new tab "Actions":
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205881648-a8072d8c-5803-4d76-b8a8-9b2fb49516c1.png">
#### 4. Upload workflow files
Upload some workflow files to `.gitea/workflows/xxx.yaml`, you can
follow the [quickstart](https://docs.github.com/en/actions/quickstart)
of GitHub Actions. Yes, Gitea Actions is compatible with GitHub Actions
in most cases, you can use the same demo:
```yaml
name: GitHub Actions Demo
run-name: ${{ github.actor }} is testing out GitHub Actions 🚀
on: [push]
jobs:
Explore-GitHub-Actions:
runs-on: ubuntu-latest
steps:
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."
- name: Check out repository code
uses: actions/checkout@v3
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
- name: List files in the repository
run: |
ls ${{ github.workspace }}
- run: echo "🍏 This job's status is ${{ job.status }}."
```
If all is well, you'll see a new run in `Actions` tab:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884473-79a874bc-171b-4aaf-acd5-0241a45c3b53.png">
#### 5. Check the logs of jobs
Click a run and you'll see the logs:
<img width="1792" alt="image"
src="https://user-images.githubusercontent.com/9418365/205884800-994b0374-67f7-48ff-be9a-4c53f3141547.png">
#### 6. Go on
You can try more examples in [the
documents](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
of GitHub Actions, then you might find a lot of bugs.
Come on, PRs are welcome.
</details>
See also: [Feature Preview: Gitea
Actions](https://blog.gitea.io/2022/12/feature-preview-gitea-actions/)
---------
Co-authored-by: a1012112796 <1012112796@qq.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2 years ago
import { initRepositoryActionView } from './components/RepoActionView.vue' ;
import { initGlobalTooltips } from './modules/tippy.ts' ;
import { initGiteaFomantic } from './modules/fomantic.ts' ;
import { initSubmitEventPolyfill , onDomReady } from './utils/dom.ts' ;
import { initRepoIssueList } from './features/repo-issue-list.ts' ;
import { initCommonIssueListQuickGoto } from './features/common-issue-list.ts' ;
import { initRepoContributors } from './features/contributors.ts' ;
import { initRepoCodeFrequency } from './features/code-frequency.ts' ;
import { initRepoRecentCommits } from './features/recent-commits.ts' ;
import { initRepoDiffCommitBranchesAndTags } from './features/repo-diff-commit.ts' ;
import { initDirAuto } from './modules/dirauto.ts' ;
import { initRepositorySearch } from './features/repo-search.ts' ;
import { initColorPickers } from './features/colorpicker.ts' ;
import { initAdminSelfCheck } from './features/admin/selfcheck.ts' ;
import { initOAuth2SettingsDisableCheckbox } from './features/oauth2-settings.ts' ;
import { initGlobalFetchAction } from './features/common-fetch-action.ts' ;
import { initScopedAccessTokenCategories } from './features/scoped-access-token.ts' ;
import {
initFootLanguageMenu ,
initGlobalDropdown ,
initGlobalTabularMenu ,
initHeadNavbarContentToggle ,
} from './features/common-page.ts' ;
import {
initGlobalButtonClickOnEnter ,
initGlobalButtons ,
initGlobalDeleteButton ,
initGlobalShowModal ,
} from './features/common-button.ts' ;
import { initGlobalEnterQuickSubmit , initGlobalFormDirtyLeaveConfirm } from './features/common-form.ts' ;
Fine tune more downdrop settings, use SVG for labels, improve Repo Topic Edit form (#23626)
Although it seems that some different purposes are mixed in this PR,
however, they are all related, and can be tested together, so I put them
together to save everyone's time.
Diff: `+79 −84`, everything becomes much better.
### Improve the dropdown settings.
Move all fomantic-init related code into our `fomantic.js`
Fine-tune some dropdown global settings, see the comments.
Also help to fix the first problem in #23625 , cc: @yp05327
The "language" menu has been simplified, and it works with small-height
window better.
### Use SVG instead of `<i class="delete icon">`
It's also done by `$.fn.dropdown.settings.templates.label` , cc:
@silverwind
### Remove incorrect `tabable` CSS class
It doesn't have CSS styles, and it was only in Vue. So it's totally
unnecessary, remove it by the way.
### Improve the Repo Topic Edit form
* Simplify the code
* Add a "Cancel" button
* Align elements
Before:
<details>
![image](https://user-images.githubusercontent.com/2114189/223325782-f09532de-0c38-4742-ba86-ed35cc9a858d.png)
</details>
After:
![image](https://user-images.githubusercontent.com/2114189/226796347-207feb0a-b3cd-4820-8a3e-01930bab1069.png)
2 years ago
initGiteaFomantic ( ) ;
initDirAuto ( ) ;
initSubmitEventPolyfill ( ) ;
function callInitFunctions ( functions : ( ( ) = > any ) [ ] ) {
// Start performance trace by accessing a URL by "https://localhost/?_ui_performance_trace=1" or "https://localhost/?key=value&_ui_performance_trace=1"
// It is a quick check, no side effect so no need to do slow URL parsing.
const initStart = performance . now ( ) ;
if ( window . location . search . includes ( '_ui_performance_trace=1' ) ) {
let results : { name : string , dur : number } [ ] = [ ] ;
for ( const func of functions ) {
const start = performance . now ( ) ;
func ( ) ;
results . push ( { name : func.name , dur : performance.now ( ) - start } ) ;
}
results = results . sort ( ( a , b ) = > b . dur - a . dur ) ;
for ( let i = 0 ; i < 20 && i < results . length ; i ++ ) {
// eslint-disable-next-line no-console
console . log ( ` performance trace: ${ results [ i ] . name } ${ results [ i ] . dur . toFixed ( 3 ) } ` ) ;
}
} else {
for ( const func of functions ) {
func ( ) ;
}
}
const initDur = performance . now ( ) - initStart ;
if ( initDur > 500 ) {
console . error ( ` slow init functions took ${ initDur . toFixed ( 3 ) } ms ` ) ;
}
}
onDomReady ( ( ) = > {
callInitFunctions ( [
initGlobalDropdown ,
initGlobalTabularMenu ,
initGlobalShowModal ,
initGlobalFetchAction ,
initGlobalTooltips ,
initGlobalButtonClickOnEnter ,
initGlobalButtons ,
initGlobalCopyToClipboardListener ,
initGlobalEnterQuickSubmit ,
initGlobalFormDirtyLeaveConfirm ,
initGlobalDeleteButton ,
initCommonOrganization ,
initCommonIssueListQuickGoto ,
initCompSearchUserBox ,
initCompWebHookEditor ,
initInstall ,
initHeadNavbarContentToggle ,
initFootLanguageMenu ,
initCommentContent ,
initContextPopups ,
initHeatmap ,
initImageDiff ,
initMarkupAnchors ,
initMarkupContent ,
initSshKeyFormParser ,
initStopwatch ,
initTableSort ,
initAutoFocusEnd ,
initFindFileInRepo ,
initCopyContent ,
initAdminCommon ,
initAdminEmails ,
initAdminUserListSearchForm ,
initAdminConfigs ,
initAdminSelfCheck ,
initDashboardRepoList ,
initNotificationCount ,
initNotificationsTable ,
initOrgTeamSearchRepoBox ,
initOrgTeamSettings ,
initRepoActivityTopAuthorsChart ,
initRepoArchiveLinks ,
initRepoBranchButton ,
initRepoCodeView ,
initRepoCommentForm ,
Actions support workflow dispatch event (#28163)
fix #23668
My plan:
* In the `actions.list` method, if workflow is selected and IsAdmin,
check whether the on event contains `workflow_dispatch`. If so, display
a `Run workflow` button to allow the user to manually trigger the run.
* Providing a form that allows users to select target brach or tag, and
these parameters can be configured in yaml
* Simple form validation, `required` input cannot be empty
* Add a route `/actions/run`, and an `actions.Run` method to handle
* Add `WorkflowDispatchPayload` struct to pass the Webhook event payload
to the runner when triggered, this payload carries the `inputs` values
and other fields, doc: [workflow_dispatch
payload](https://docs.github.com/en/webhooks/webhook-events-and-payloads#workflow_dispatch)
Other PRs
* the `Workflow.WorkflowDispatchConfig()` method still return non-nil
when workflow_dispatch is not defined. I submitted a PR
https://gitea.com/gitea/act/pulls/85 to fix it. Still waiting for them
to process.
Behavior should be same with github, but may cause confusion. Here's a
quick reminder.
*
[Doc](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)
Said: This event will `only` trigger a workflow run if the workflow file
is `on the default branch`.
* If the workflow yaml file only exists in a non-default branch, it
cannot be triggered. (It will not even show up in the workflow list)
* If the same workflow yaml file exists in each branch at the same time,
the version of the default branch is used. Even if `Use workflow from`
selects another branch
![image](https://github.com/go-gitea/gitea/assets/3114995/4bf596f3-426b-48e8-9b8f-0f6d18defd79)
```yaml
name: Docker Image CI
on:
workflow_dispatch:
inputs:
logLevel:
description: 'Log level'
required: true
default: 'warning'
type: choice
options:
- info
- warning
- debug
tags:
description: 'Test scenario tags'
required: false
type: boolean
boolean_default_true:
description: 'Test scenario tags'
required: true
type: boolean
default: true
boolean_default_false:
description: 'Test scenario tags'
required: false
type: boolean
default: false
environment:
description: 'Environment to run tests against'
type: environment
required: true
default: 'environment values'
number_required_1:
description: 'number '
type: number
required: true
default: '100'
number_required_2:
description: 'number'
type: number
required: true
default: '100'
number_required_3:
description: 'number'
type: number
required: true
default: '100'
number_1:
description: 'number'
type: number
required: false
number_2:
description: 'number'
type: number
required: false
number_3:
description: 'number'
type: number
required: false
env:
inputs_logLevel: ${{ inputs.logLevel }}
inputs_tags: ${{ inputs.tags }}
inputs_boolean_default_true: ${{ inputs.boolean_default_true }}
inputs_boolean_default_false: ${{ inputs.boolean_default_false }}
inputs_environment: ${{ inputs.environment }}
inputs_number_1: ${{ inputs.number_1 }}
inputs_number_2: ${{ inputs.number_2 }}
inputs_number_3: ${{ inputs.number_3 }}
inputs_number_required_1: ${{ inputs.number_required_1 }}
inputs_number_required_2: ${{ inputs.number_required_2 }}
inputs_number_required_3: ${{ inputs.number_required_3 }}
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- run: ls -la
- run: env | grep inputs
- run: echo ${{ inputs.logLevel }}
- run: echo ${{ inputs.boolean_default_false }}
```
![image](https://github.com/go-gitea/gitea/assets/3114995/a58a842d-a0ff-4618-bc6d-83a9596d07c8)
![image](https://github.com/go-gitea/gitea/assets/3114995/44a7cca5-7bd4-42a9-8723-91751a501c88)
---------
Co-authored-by: TKaxv_7S <954067342@qq.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Denys Konovalov <kontakt@denyskon.de>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
3 months ago
initBranchSelectorTabs ,
initRepoEllipsisButton ,
initRepoDiffCommitBranchesAndTags ,
initRepoEditor ,
initRepoGraphGit ,
initRepoIssueContentHistory ,
initRepoIssueDue ,
initRepoIssueList ,
initRepoIssueSidebarList ,
initArchivedLabelHandler ,
initRepoIssueReferenceRepositorySearch ,
initRepoIssueTimeTracking ,
initRepoIssueWipTitle ,
initRepoMigration ,
initRepoMigrationStatusChecker ,
initRepoProject ,
initRepoPullRequestMergeInstruction ,
initRepoPullRequestAllowMaintainerEdit ,
initRepoPullRequestReview ,
initRepoRelease ,
initRepoReleaseNew ,
initRepoSettingGitHook ,
initRepoSettingSearchTeamBox ,
initRepoSettingsCollaboration ,
initRepoTemplateSearch ,
initRepoTopicBar ,
initRepoWikiForm ,
initRepository ,
initRepositoryActionView ,
initRepositorySearch ,
initRepoContributors ,
initRepoCodeFrequency ,
initRepoRecentCommits ,
initCommitStatuses ,
initCaptcha ,
initUserAuthOauth2 ,
initUserAuthWebAuthn ,
initUserAuthWebAuthnRegister ,
initUserSettings ,
initRepoDiffView ,
initPdfViewer ,
initScopedAccessTokenCategories ,
initColorPickers ,
initOAuth2SettingsDisableCheckbox ,
] ) ;
} ) ;