- 02 Apr, 2019 6 commits
-
-
Lunny Xiao authored
-
GiteaBot authored
-
mrsdizzie authored
This is a header used to suggest mail servers not to respond to a message with an auto-responder: https://docs.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-oxcmail/ced68690-498a-4567-9d14-5c01f974d8b1 This header is also used by github and gitlab in outgoing messages. Fixes #6484
-
zeripath authored
* Panic don't fatal on create new logger Fixes #5854 Signed-off-by:
Andrew Thornton <art27@cantab.net> * partial broken * Update the logging infrastrcture Signed-off-by:
Andrew Thornton <art27@cantab.net> * Reset the skip levels for Fatal and Error Signed-off-by:
Andrew Thornton <art27@cantab.net> * broken ncsa * More log.Error fixes Signed-off-by:
Andrew Thornton <art27@cantab.net> * Remove nal * set log-levels to lowercase * Make console_test test all levels * switch to lowercased levels * OK now working * Fix vetting issues * Fix lint * Fix tests * change default logging to match current gitea * Improve log testing Signed-off-by:
Andrew Thornton <art27@cantab.net> * reset error skip levels to 0 * Update documentation and access logger configuration * Redirect the router log back to gitea if redirect macaron log but also allow setting the log level - i.e. TRACE * Fix broken level caching * Refactor the router log * Add Router logger * Add colorizing options * Adjust router colors * Only create logger if they will be used * update app.ini.sample * rename Attribute ColorAttribute * Change from white to green for function * Set fatal/error levels * Restore initial trace logger * Fix Trace arguments in modules/auth/auth.go * Properly handle XORMLogger * Improve admin/config page * fix fmt * Add auto-compression of old logs * Update error log levels * Remove the unnecessary skip argument from Error, Fatal and Critical * Add stacktrace support * Fix tests * Remove x/sync from vendors? * Add stderr option to console logger * Use filepath.ToSlash to protect against Windows in tests * Remove prefixed underscores from names in colors.go * Remove not implemented database logger This was removed from Gogs on 4 Mar 2016 but left in the configuration since then. * Ensure that log paths are relative to ROOT_PATH * use path.Join * rename jsonConfig to logConfig * Rename "config" to "jsonConfig" to make it clearer * Requested changes * Requested changes: XormLogger * Try to color the windows terminal If successful default to colorizing the console logs * fixup * Colorize initially too * update vendor * Colorize logs on default and remove if this is not a colorizing logger * Fix documentation * fix test * Use go-isatty to detect if on windows we are on msys or cygwin * Fix spelling mistake * Add missing vendors * More changes * Rationalise the ANSI writer protection * Adjust colors on advice from @0x5c * Make Flags a comma separated list * Move to use the windows constant for ENABLE_VIRTUAL_TERMINAL_PROCESSING * Ensure matching is done on the non-colored message - to simpify EXPRESSION
-
Lunny Xiao authored
-
John Olheiser authored
Signed-off-by:
jolheiser <john.olheiser@gmail.com>
-
- 01 Apr, 2019 3 commits
-
-
GiteaBot authored
-
Richard Mahn authored
-
glaszig authored
* support custom file name in `gitea dump` command * simpler approach to handle default dump file name in `gitea dump` command
-
- 31 Mar, 2019 1 commit
-
-
BetaCat authored
-
- 30 Mar, 2019 1 commit
-
-
zeripath authored
* fix rel-ref * fixup
-
- 29 Mar, 2019 1 commit
-
-
Ilya authored
Signed-off-by:
Ilya Pavlov <ilux@cpan.org>
-
- 28 Mar, 2019 2 commits
- 27 Mar, 2019 5 commits
-
-
oscar.lofwenhamn authored
* Make Ghost not link to 404 page * Make correct localization label show * Create and use GetLastEventLabelFake for when a Ghost user has made the action, thus not linking to a user profile * Add corresponding _fake entries to locale_en-US * Make Ghost avatar not link to 404 page * Make Ghost on milestone_issues not link to 404 page
-
John Olheiser authored
* Changelog 1.8.0 rc2 (#6451) * Changelog 1.7.5 (#6444) (#6448) Signed-off-by:
jolheiser <john.olheiser@gmail.com>
-
mrsdizzie authored
Make sure Processors that work on full links are run first so that something matching another pattern doesn't alter a link before we get to it, for example: https://stackoverflow.com/questions/2896191/what-is-go-used-fore Fixes #4813
-
Mura Li authored
* Migrate to go modules * make vendor * Update mvdan.cc/xurls * make vendor * Update code.gitea.io/git * make fmt-check * Update github.com/go-sql-driver/mysql * make vendor
-
Lunny Xiao authored
* move code.gitea.io/git to code.gitea.io/gitea/modules/git * fix imports * fix fmt * fix misspell * remove wrong tests data * fix unit tests * fix tests * fix tests * fix tests * fix tests * fix tests * enable Debug to trace the failure tests * fix tests * fix tests * fix tests * fix tests * fix tests * comment commit count tests since git clone depth is 50 * fix tests * update from code.gitea.io/git * revert change to makefile
-
- 26 Mar, 2019 3 commits
-
-
mrsdizzie authored
* Clean up ref name rules Clean up checks on reference names to better conform to the guideline here: https://git-scm.com/docs/git-check-ref-format This fixes half of #6321 * Update branch create integration test According to: https://git-scm.com/docs/git-check-ref-format And: git check-ref-format "master/feature=test1" This is a valid branch name and we should not be testing for it to fail.
-
Segev Finer authored
Signed-off-by:
Segev Finer <segev@codeocean.com>
-
techknowlogick authored
-
- 25 Mar, 2019 2 commits
-
-
Allen Wild authored
Set Err_Interval in the context data so that the mirror interval box is highlighted red as expected. Clear Err_RepoName for the mirror and advanced actions. repo_name is not set by these forms, causing auth.validate() to set the Err_RepoName before SettingsPost is called, which would lead to the repository name box getting erroneously highlighted red. Fixes: https://github.com/go-gitea/gitea/issues/6396
-
silverwind authored
Fixes: https://github.com/go-gitea/gitea/pull/6357
-
- 24 Mar, 2019 1 commit
-
-
kolaente authored
-
- 22 Mar, 2019 3 commits
-
-
GiteaBot authored
-
Richard Mahn authored
-
Lunny Xiao authored
-
- 21 Mar, 2019 4 commits
-
-
Roland Koebler authored
* Markdown: enable some more extensions Improve Markdown-rendering by enabling some extensions: - enable definitions lists - enable footnotes - enable header-ids and automatically generate header-ids (for linking to README-sections or creating table-of-contents for larger READMEs) * Markdown: update and exted tests Update and add tests for additionally enabled Markdown-extensions.
-
mrsdizzie authored
redirect_to holds a value that we want to redirect back to after login. This value can be a path with intentonally escaped values and we should not unescape it. Fixes #4475
-
GiteaBot authored
-
Lunny Xiao authored
-
- 20 Mar, 2019 3 commits
-
-
GiteaBot authored
-
Lunny Xiao authored
fix migrations 82 to ignore unsynced tags between database and git data and missing is_archived on repository table (#6387)
-
NateScarlet authored
Resolve #6004
-
- 19 Mar, 2019 5 commits
-
-
mrsdizzie authored
Include the current CustomPath location in the admin section and also display GITEA_WORK_DIR and/or GITEA_CUSTOM env var if they are set. Right now there is no easy way to see this information, and if you try and help most users they won't be able to tell you anything about these values -- just that their custom template isn't working, files aren't in the right place, etc... Now you can see all paths and if they were set by ENV or not.
-
Lanre Adelowo authored
-
GiteaBot authored
-
Lunny Xiao authored
fix bug manifest.json will not request with cookie so that session will created every request (#6372)
-
GiteaBot authored
-