[Bug] Checkbox at RepoSetting for CI does not work #4115

Closed
opened 2025-11-02 05:38:49 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @6543 on GitHub (Oct 14, 2019).

I'll update this issue later on - short description

the checkbox of an CI in the settings (protected branch) dont behave like has no function

either make a list

  • with
  • souch points

or give the a function (only if checked CI will be checked/has to aprove PR)

Originally created by @6543 on GitHub (Oct 14, 2019). I'll update this issue later on - short description the checkbox of an CI in the settings (protected branch) dont behave like has no function either make a list * with * souch points or give the a function (only if checked CI will be checked/has to aprove PR)
GiteaMirror added the topic/uitype/bug labels 2025-11-02 05:38:49 -06:00
Author
Owner

@6543 commented on GitHub (Oct 23, 2019):

Bildschirmfoto zu 2019-10-23 00-06-37

-> is this aktive or not ?

= it is ...

@6543 commented on GitHub (Oct 23, 2019): ![Bildschirmfoto zu 2019-10-23 00-06-37](https://user-images.githubusercontent.com/24977596/67346997-fe058f00-f540-11e9-9b9d-c0bc047bdc22.png) -> is this aktive or not ? = it is ...
Author
Owner

@6543 commented on GitHub (Nov 2, 2019):

templates/repo/settings/protected_branch.tmpl: L135

<input class="enable-whitelist" name="status_check_contexts" value="{{.}}" type="checkbox" {{if $.is_context_require}}{{if call $.is_context_required .}}checked{{end}}{{end}}>

@lafriks @lunny you added/changed this code at #7481 do you have any idears why this happens?

@6543 commented on GitHub (Nov 2, 2019): templates/repo/settings/protected_branch.tmpl: L135 `<input class="enable-whitelist" name="status_check_contexts" value="{{.}}" type="checkbox" {{if $.is_context_require}}{{if call $.is_context_required .}}checked{{end}}{{end}}>` @lafriks @lunny you added/changed this code at #7481 do you have any idears why this happens?
Author
Owner

@6543 commented on GitHub (Nov 2, 2019):

I found a wrong var: https://github.com/go-gitea/gitea/pull/8799

but i can NOT test, if this will fix it (have no local CI running), I can verify if patch is aplyed to gitea.com :(

EDIT: I can ... (note for other devs:)

fake a CI status using the API http://<your-gitea-server>/api/swagger#/repository/repoCreateStatus
{
  "context":"fake-context",
  "description": "fake-description",
  "state": "success",
  "target_url": "https://gnu.org"
}

+ ApiTocken
@6543 commented on GitHub (Nov 2, 2019): I found a wrong var: https://github.com/go-gitea/gitea/pull/8799 but i can NOT test, if this will fix it (have no local CI running), I can verify if patch is aplyed to gitea.com :( EDIT: I can ... (note for other devs:) ``` fake a CI status using the API http://<your-gitea-server>/api/swagger#/repository/repoCreateStatus { "context":"fake-context", "description": "fake-description", "state": "success", "target_url": "https://gnu.org" } + ApiTocken ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4115