Skip to content
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

Add option to ignore whitespace in diffs #2180

Closed
tobias-- opened this issue Jul 19, 2017 · 3 comments
Closed

Add option to ignore whitespace in diffs #2180

tobias-- opened this issue Jul 19, 2017 · 3 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@tobias--
Copy link

  • Gitea version (or commit ref): 1.1.2

Description

It would be great to have the ability to ignore whitespace in diffs on demand. For example, Github allows you to do this by adding '?w=1' to the URL. See https://github.com/blog/967-github-secrets
@tonivj5
Copy link
Contributor

tonivj5 commented Jul 19, 2017

woow, that trick is awesome! Thanks 😄

@lafriks lafriks added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Jul 19, 2017
@lafriks lafriks added this to the 1.x.x milestone Jul 19, 2017
@tobias--
Copy link
Author

I just noticed: This issue duplicates #716.

@andreynering
Copy link
Contributor

@tobias-- In this case let's close this in favor of #716

@lunny lunny removed this from the 1.x.x milestone Aug 24, 2017
@lunny lunny added issue/duplicate The issue has already been reported. and removed type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Aug 24, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
6543 pushed a commit to 6543-forks/gitea that referenced this issue Feb 26, 2024
@Gusted @earl-warren
[GITEA] Fix API inconsistencies
bbe5a88 
- Document the correct content types for Git archives. Add code that
actually sets the correct application type for `.zip` and `.tar.gz`.
- When an action (POST/PUT/DELETE method) was successful, an 204 status
code should be returned instead of status code 200.
- Add and adjust integration testing.
- Resolves go-gitea#2180
- Resolves go-gitea#2181

(cherry picked from commit 6c8c4512b530e966557a5584efbbb757638b3429)
(cherry picked from commit 3f74bcb14df99ee75a170813979beb5ce04c8027)
(cherry picked from commit 6ed9057fd76b2d5d0dfdb3c663367ae861ab8093)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lunny @lafriks @tobias-- @andreynering @tonivj5