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.
2022-03-30 08:52:24 +03:00
// bootstrap module must be the first one to be imported, it handles webpack lazy-loading and global errors
import './bootstrap.js' ;
2020-02-24 00:34:28 +03:00
2022-01-29 00:00:11 +03:00
import $ from 'jquery' ;
2021-10-15 05:35:26 +03:00
import { initVueEnv } from './components/VueComponentLoader.js' ;
import { initRepoActivityTopAuthorsChart } from './components/RepoActivityTopAuthors.vue' ;
import { initDashboardRepoList } from './components/DashboardRepoList.js' ;
2022-12-23 19:03:11 +03:00
import { attachTribute } from './features/tribute.js' ;
import { initGlobalCopyToClipboardListener } from './features/clipboard.js' ;
import { initContextPopups } from './features/contextpopup.js' ;
import { initRepoGraphGit } from './features/repo-graph.js' ;
import { initHeatmap } from './features/heatmap.js' ;
import { initImageDiff } from './features/imagediff.js' ;
import { initRepoMigration } from './features/repo-migration.js' ;
import { initRepoProject } from './features/repo-projects.js' ;
import { initServiceWorker } from './features/serviceworker.js' ;
import { initTableSort } from './features/tablesort.js' ;
2022-10-17 02:29:26 +03:00
import { initAdminUserListSearchForm } from './features/admin/users.js' ;
import { initAdminConfigs } from './features/admin/config.js' ;
2021-05-07 11:43:41 +03:00
import { initMarkupAnchors } from './markup/anchors.js' ;
2021-10-16 20:28:04 +03:00
import { initNotificationCount , initNotificationsTable } from './features/notification.js' ;
2021-11-09 12:27:25 +03:00
import { initRepoIssueContentHistory } from './features/repo-issue-content.js' ;
2021-01-21 17:51:52 +03:00
import { initStopwatch } from './features/stopwatch.js' ;
2022-06-09 14:15:08 +03:00
import { initFindFileInRepo } from './features/repo-findfile.js' ;
2021-10-16 20:28:04 +03:00
import { initCommentContent , initMarkupContent } from './markup/content.js' ;
2022-12-23 19:03:11 +03:00
import { initDiffFileTree } from './features/repo-diff-filetree.js' ;
2021-10-16 20:28:04 +03:00
import { initUserAuthLinkAccountView , initUserAuthOauth2 } from './features/user-auth.js' ;
import {
initRepoDiffConversationForm ,
initRepoDiffFileViewToggle ,
2021-11-09 12:27:25 +03:00
initRepoDiffReviewButton , initRepoDiffShowMore ,
2021-10-16 20:28:04 +03:00
} from './features/repo-diff.js' ;
import {
initRepoIssueDue ,
initRepoIssueList ,
initRepoIssueReferenceRepositorySearch ,
initRepoIssueTimeTracking ,
initRepoIssueWipTitle ,
initRepoPullRequestMergeInstruction ,
2022-04-28 18:45:33 +03:00
initRepoPullRequestAllowMaintainerEdit ,
2021-10-16 20:28:04 +03:00
initRepoPullRequestReview ,
} from './features/repo-issue.js' ;
2022-04-26 22:09:46 +03:00
import {
initRepoEllipsisButton ,
initRepoCommitLastCommitLoader ,
initCommitStatuses ,
} from './features/repo-commit.js' ;
2021-10-16 20:28:04 +03:00
import {
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.
2022-03-30 08:52:24 +03:00
checkAppUrl ,
2021-10-16 20:28:04 +03:00
initFootLanguageMenu ,
initGlobalButtonClickOnEnter ,
initGlobalButtons ,
initGlobalCommon ,
initGlobalDropzone ,
initGlobalEnterQuickSubmit ,
initGlobalFormDirtyLeaveConfirm ,
initGlobalLinkActions ,
initHeadNavbarContentToggle ,
2022-08-09 15:37:34 +03:00
initGlobalTooltips ,
2021-10-16 20:28:04 +03:00
} from './features/common-global.js' ;
import { initRepoTopicBar } from './features/repo-home.js' ;
2022-10-17 02:29:26 +03:00
import { initAdminEmails } from './features/admin/emails.js' ;
import { initAdminCommon } from './features/admin/common.js' ;
2021-10-16 20:28:04 +03:00
import { initRepoTemplateSearch } from './features/repo-template.js' ;
import { initRepoCodeView } from './features/repo-code.js' ;
import { initSshKeyFormParser } from './features/sshkey-helper.js' ;
import { initUserSettings } from './features/user-settings.js' ;
import { initRepoArchiveLinks } from './features/repo-common.js' ;
import { initRepoMigrationStatusChecker } from './features/repo-migrate.js' ;
import {
initRepoSettingGitHook ,
initRepoSettingsCollaboration ,
initRepoSettingSearchTeamBox ,
} from './features/repo-settings.js' ;
2022-05-07 21:28:10 +03:00
import { initViewedCheckboxListenerFor } from './features/pull-view-file.js' ;
2021-10-16 20:28:04 +03:00
import { initOrgTeamSearchRepoBox , initOrgTeamSettings } from './features/org-team.js' ;
2022-01-14 18:03:31 +03:00
import { initUserAuthWebAuthn , initUserAuthWebAuthnRegister } from './features/user-auth-webauthn.js' ;
2021-10-16 20:28:04 +03:00
import { initRepoRelease , initRepoReleaseEditor } from './features/repo-release.js' ;
import { initRepoEditor } from './features/repo-editor.js' ;
2021-11-09 12:27:25 +03:00
import { initCompSearchUserBox } from './features/comp/SearchUserBox.js' ;
2021-10-16 20:28:04 +03:00
import { initInstall } from './features/install.js' ;
2021-11-09 12:27:25 +03:00
import { initCompWebHookEditor } from './features/comp/WebHookEditor.js' ;
2021-10-16 20:28:04 +03:00
import { initCommonIssue } from './features/common-issue.js' ;
import { initRepoBranchButton } from './features/repo-branch.js' ;
import { initCommonOrganization } from './features/common-organization.js' ;
import { initRepoWikiForm } from './features/repo-wiki.js' ;
import { initRepoCommentForm , initRepository } from './features/repo-legacy.js' ;
2022-06-12 15:08:23 +03:00
import { initFormattingReplacements } from './features/formatting.js' ;
2022-08-10 16:20:10 +03:00
import { initMcaptcha } from './features/mcaptcha.js' ;
2022-11-21 12:59:42 +03:00
import { initCopyContent } from './features/copycontent.js' ;
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>
2023-01-31 04:45:19 +03:00
import { initRepositoryActionView } from './components/RepoActionView.vue' ;
2022-06-12 15:08:23 +03:00
// Run time-critical code as soon as possible. This is safe to do because this
// script appears at the end of <body> and rendered HTML is accessible at that point.
initFormattingReplacements ( ) ;
2019-11-13 17:52:13 +03:00
2020-01-12 05:57:32 +03:00
// Silence fomantic's error logging when tabs are used without a target content element
$ . fn . tab . settings . silent = true ;
2022-02-22 22:43:11 +03:00
// Disable the behavior of fomantic to toggle the checkbox when you press enter on a checkbox element.
$ . fn . checkbox . settings . enableEnterKey = false ;
2019-11-15 00:39:51 +03:00
2021-10-16 20:28:04 +03:00
initVueEnv ( ) ;
2021-11-09 12:27:25 +03:00
$ ( document ) . ready ( ( ) => {
2021-10-16 20:28:04 +03:00
initGlobalCommon ( ) ;
2021-11-09 12:27:25 +03:00
2022-08-09 15:37:34 +03:00
initGlobalTooltips ( ) ;
2021-11-09 12:27:25 +03:00
initGlobalButtonClickOnEnter ( ) ;
initGlobalButtons ( ) ;
initGlobalCopyToClipboardListener ( ) ;
2021-10-16 20:28:04 +03:00
initGlobalDropzone ( ) ;
2021-11-09 12:27:25 +03:00
initGlobalEnterQuickSubmit ( ) ;
initGlobalFormDirtyLeaveConfirm ( ) ;
2021-10-16 20:28:04 +03:00
initGlobalLinkActions ( ) ;
2021-11-09 12:27:25 +03:00
attachTribute ( document . querySelectorAll ( '#content, .emoji-input' ) ) ;
2019-11-15 00:39:51 +03:00
2021-10-16 20:28:04 +03:00
initCommonIssue ( ) ;
2021-11-09 12:27:25 +03:00
initCommonOrganization ( ) ;
2019-11-15 00:39:51 +03:00
2021-11-09 12:27:25 +03:00
initCompSearchUserBox ( ) ;
initCompWebHookEditor ( ) ;
2019-11-15 00:39:51 +03:00
initInstall ( ) ;
2021-11-09 12:27:25 +03:00
initHeadNavbarContentToggle ( ) ;
initFootLanguageMenu ( ) ;
initCommentContent ( ) ;
initContextPopups ( ) ;
initHeatmap ( ) ;
initImageDiff ( ) ;
initMarkupAnchors ( ) ;
initMarkupContent ( ) ;
initServiceWorker ( ) ;
initSshKeyFormParser ( ) ;
initStopwatch ( ) ;
initTableSort ( ) ;
2022-06-09 14:15:08 +03:00
initFindFileInRepo ( ) ;
2022-11-21 12:59:42 +03:00
initCopyContent ( ) ;
2021-11-09 12:27:25 +03:00
2021-10-16 20:28:04 +03:00
initAdminCommon ( ) ;
2021-11-09 12:27:25 +03:00
initAdminEmails ( ) ;
initAdminUserListSearchForm ( ) ;
2022-10-17 02:29:26 +03:00
initAdminConfigs ( ) ;
2021-11-09 12:27:25 +03:00
2021-10-15 05:35:26 +03:00
initDashboardRepoList ( ) ;
2021-11-09 12:27:25 +03:00
initNotificationCount ( ) ;
initNotificationsTable ( ) ;
initOrgTeamSearchRepoBox ( ) ;
2021-10-16 20:28:04 +03:00
initOrgTeamSettings ( ) ;
2021-11-09 12:27:25 +03:00
initRepoActivityTopAuthorsChart ( ) ;
initRepoArchiveLinks ( ) ;
initRepoBranchButton ( ) ;
initRepoCodeView ( ) ;
initRepoCommentForm ( ) ;
2021-11-23 05:44:38 +03:00
initRepoEllipsisButton ( ) ;
2021-11-09 12:27:25 +03:00
initRepoCommitLastCommitLoader ( ) ;
initRepoDiffConversationForm ( ) ;
initRepoDiffFileViewToggle ( ) ;
initRepoDiffReviewButton ( ) ;
initRepoDiffShowMore ( ) ;
2022-09-27 08:22:19 +03:00
initDiffFileTree ( ) ;
2021-11-09 12:27:25 +03:00
initRepoEditor ( ) ;
initRepoGraphGit ( ) ;
initRepoIssueContentHistory ( ) ;
initRepoIssueDue ( ) ;
2021-10-16 20:28:04 +03:00
initRepoIssueList ( ) ;
2021-11-09 12:27:25 +03:00
initRepoIssueReferenceRepositorySearch ( ) ;
2021-10-16 20:28:04 +03:00
initRepoIssueTimeTracking ( ) ;
initRepoIssueWipTitle ( ) ;
2021-11-09 12:27:25 +03:00
initRepoMigration ( ) ;
2021-10-16 20:28:04 +03:00
initRepoMigrationStatusChecker ( ) ;
2021-11-09 12:27:25 +03:00
initRepoProject ( ) ;
2021-10-16 20:28:04 +03:00
initRepoPullRequestMergeInstruction ( ) ;
2022-04-28 18:45:33 +03:00
initRepoPullRequestAllowMaintainerEdit ( ) ;
2021-11-09 12:27:25 +03:00
initRepoPullRequestReview ( ) ;
2021-10-16 20:28:04 +03:00
initRepoRelease ( ) ;
2021-11-09 12:27:25 +03:00
initRepoReleaseEditor ( ) ;
initRepoSettingGitHook ( ) ;
initRepoSettingSearchTeamBox ( ) ;
2021-10-16 20:28:04 +03:00
initRepoSettingsCollaboration ( ) ;
2021-11-09 12:27:25 +03:00
initRepoTemplateSearch ( ) ;
initRepoTopicBar ( ) ;
initRepoWikiForm ( ) ;
initRepository ( ) ;
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>
2023-01-31 04:45:19 +03:00
initRepositoryActionView ( ) ;
2019-11-15 00:39:51 +03:00
2022-04-26 22:09:46 +03:00
initCommitStatuses ( ) ;
2022-08-10 16:20:10 +03:00
initMcaptcha ( ) ;
2022-04-26 22:09:46 +03:00
2021-11-09 12:27:25 +03:00
initUserAuthLinkAccountView ( ) ;
initUserAuthOauth2 ( ) ;
2022-01-14 18:03:31 +03:00
initUserAuthWebAuthn ( ) ;
initUserAuthWebAuthnRegister ( ) ;
2021-11-09 12:27:25 +03:00
initUserSettings ( ) ;
2022-05-07 21:28:10 +03:00
initViewedCheckboxListenerFor ( ) ;
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.
2022-03-30 08:52:24 +03:00
checkAppUrl ( ) ;
2019-11-15 00:39:51 +03:00
} ) ;