Skip to content

fix fading menu in arc-green theme #5128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 20, 2018
Merged

fix fading menu in arc-green theme #5128

merged 5 commits into from
Oct 20, 2018

Conversation

glaszig
Copy link
Contributor

@glaszig glaszig commented Oct 19, 2018

the menu faded white because it missed proper styling.
only visible on viewports narrower than 1200px.

before after
before after

the menu faded white because it missed proper styling.
only visible on viewports narrower than 1200px.
@lunny lunny added the topic/ui Change the appearance of the Gitea UI label Oct 20, 2018
@bkcsoft bkcsoft added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Oct 20, 2018
@bkcsoft bkcsoft added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Oct 20, 2018
@lafriks
Copy link
Member

lafriks commented Oct 20, 2018

please run make generate-stylesheets, I can't seem to be able to push your branch.

@glaszig
Copy link
Contributor Author

glaszig commented Oct 20, 2018

@lafriks done.

@codecov-io
Copy link

Codecov Report

Merging #5128 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5128      +/-   ##
==========================================
- Coverage    37.4%   37.39%   -0.02%     
==========================================
  Files         308      308              
  Lines       45605    45605              
==========================================
- Hits        17057    17052       -5     
- Misses      26091    26095       +4     
- Partials     2457     2458       +1
Impacted Files Coverage Δ
models/repo_indexer.go 50.84% <0%> (-2.12%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2227446...099f69a. Read the comment docs.

@techknowlogick
Copy link
Member

techknowlogick commented Oct 20, 2018 via email

@techknowlogick techknowlogick merged commit 2313121 into go-gitea:master Oct 20, 2018
@glaszig glaszig deleted the patch-1 branch March 30, 2019 19:08
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this pull request Jan 23, 2025
…tication

- The Conan and Container packages use a different type of
authentication. It first authenticates via the regular way (api tokens
or user:password, handled via `auth.Basic`) and then generates a JWT
token that is used by the package software (such as Docker) to do the
action they wanted to do. This JWT token didn't properly propagate the
API scopes that the token was generated for, and thus could lead to a
'scope escalation' within the Conan and Container packages, read
access to write access.
- Store the API scope in the JWT token, so it can be propagated on
subsequent calls that uses that JWT token.
- Integration test added.
- Resolves go-gitea#5128

(cherry picked from commit 5a871f6)
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this pull request Jan 23, 2025
…tication

- The Conan and Container packages use a different type of
authentication. It first authenticates via the regular way (api tokens
or user:password, handled via `auth.Basic`) and then generates a JWT
token that is used by the package software (such as Docker) to do the
action they wanted to do. This JWT token didn't properly propagate the
API scopes that the token was generated for, and thus could lead to a
'scope escalation' within the Conan and Container packages, read
access to write access.
- Store the API scope in the JWT token, so it can be propagated on
subsequent calls that uses that JWT token.
- Integration test added.
- Resolves go-gitea#5128

(cherry picked from commit 5a871f6)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/ui Change the appearance of the Gitea UI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants