Skip to content

Subfeature request on #2211: Allow hiding tracked time from unregistered/not signed in users #2349

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.

Sign up for GitHub

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

Jump to bottom
Open
daviian opened this issue Aug 21, 2017 · 4 comments
Open

Subfeature request on #2211: Allow hiding tracked time from unregistered/not signed in users #2349

daviian opened this issue Aug 21, 2017 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented outdated/theme/timetracker type/enhancement An improvement of existing functionality

Comments

@daviian
Copy link
Member

daviian commented Aug 21, 2017

Follow-up feature request on #2211

Description

It would be great to allow hiding of tracked time from unregistered or not signed in users.
If you have a public repository and thus publicly available issues it is a must have for organizations to hide tracked time, because mostly they are internals and not destined for the public.

A solution would be to have a settings besides enabling time tracking in the repository to define the visibility/access to tracked time.
@lunny
Copy link
Member

lunny commented Aug 22, 2017

@daviian maybe just comment on #2211 since that PR is not merged.

@daviian
Copy link
Member Author

daviian commented Aug 22, 2017 •
edited
Loading

I did, but was told to open a new issue ;-) #2211 (comment)

@lunny lunny added the type/enhancement An improvement of existing functionality label Aug 22, 2017
@lunny lunny added this to the 1.x.x milestone Aug 22, 2017
@stale
Copy link

stale bot commented Feb 13, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 13, 2019
@stale
Copy link

stale bot commented Feb 27, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Feb 27, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Feb 28, 2019
@lunny lunny reopened this Feb 28, 2019
Open
@lunny lunny removed this from the 1.x.x milestone Mar 20, 2023
6543 pushed a commit to 6543-forks/gitea that referenced this issue Feb 26, 2024
Merge pull request 'Preview: set font-size on preview content' (go-gi…
1e364cc 
…tea#2349) from gusted/forgejo-preview-fontsize into forgejo

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/2349
Reviewed-by: Earl Warren <[email protected]>
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
@Gusted
Preview: set font-size on preview content
a904558 
- Backport of go-gitea#2349
- When previewing the content in a review, no font size was set. This
resulted in the previewed content being bigger than other text and
therefor creating an noticable inconsistency.
- Set the font size of the previewed content, 14px, this is consistent
with how the content would be rendered.
- `comment-code-cloud` is the class used for the review boxes.
`.ui.tab.markup` means it only applies to the preview tab.

(cherry picked from commit b1aabbf)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented outdated/theme/timetracker type/enhancement An improvement of existing functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lunny @daviian @noerw