Skip to content

Release/v1.7 #1

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 8 commits into from
Mar 14, 2019
Merged

Release/v1.7 #1

merged 8 commits into from
Mar 14, 2019

Conversation

mrsdizzie
Copy link
Owner

Please check the following:

  1. Make sure you are targeting the master branch, pull requests on release branches are only allowed for bug fixes.
  2. Read contributing guidelines: https://github.com/go-gitea/gitea/blob/master/CONTRIBUTING.md
  3. Describe what your pull request does and which issue you're targeting (if any)

You MUST delete the content above including this line before posting, otherwise your pull request will be invalid.

jolheiser and others added 8 commits February 25, 2019 21:05
* Add Changelog for 1.7.3
* fix display dashboard even if require to change password

* fix comments
#6246)

* Fix #5580 : Make organization dropdown scrollable when using mouse wheel.

* build less file with old makefile
* Proposed changelog for 1.7.4

Signed-off-by: jolheiser <[email protected]>

* Updated security fix description with @zeripath suggestion.

* Added 6292

* Update CHANGELOG.md

* Update CHANGELOG.md
@mrsdizzie mrsdizzie merged this pull request into mrsdizzie:release/v1.7 Mar 14, 2019
mrsdizzie added a commit that referenced this pull request Mar 28, 2019
Update autolinks to match what github does here:

Issue in same repo: #1
Issue in different repo: org/repo#1

Fixes go-gitea#6264
mrsdizzie added a commit that referenced this pull request Apr 15, 2019
* Improve issue autolinks

Update autolinks to match what github does here:

Issue in same repo: #1
Issue in different repo: org/repo#1

Fixes go-gitea#6264

* Use setting.AppURL when parsing URL

Using setting.AppURL here is a more reliable way of parsing the current
URL and what other functions in this file seem to use.

* Make ComposeMetas always return a valid context

* Add per repository markdown renderers for better context

* Update for use of context metas

Now that we include the user and repo name inside context metas, update
various code and tests for this new logic
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants