The syntax of the gitea Makefile is not platform-agnostic and is
specific to the GNU version of `make`. BSD platforms such as FreeBSD
ship with bmake (BSD make) as their default `make` program; attempting
to compile gitea by simply executing `make` causes a wall of errors to
show as a result of syntax incompatible with BSD make.
If a file named `BSDmakefile` is present, `bmake` will give it
preference over a generic `Makefile`. This `BSDmakefile` is taken from
the BSD-licensed `gmake-proxy` project [0], which transparently proxies
all `make` commands to `gmake` (GNU make) on systems where `bmake` is
the default, and if `gmake` is not installed an error message is
displayed.
[0]: https://github.com/neosmart/gmake-proxy
* Implemented basic api endpoint to manage deadlines
* Fixed checking for permissions
* Updating a deadline from the ui is now entirely done via the api
* cleanup
* Cosmetics
* fixed lint + fmt
* Added swagger model definition for deadline response
* Updated gitea-sdk
* Updated gitea-sdk
* More cleanup
* Generate swagger json
* Merge branch 'master' of https://github.com/go-gitea/gitea into issue-due-date-api
# Conflicts:
# public/swagger.v1.json
* Fixed permission to update a deadline via api
* Re-added form to change a deadline
* Added client-side validation + not ignore error messages from the api
* Added locale for error message
* Merge branch 'master' of https://github.com/go-gitea/gitea
# Conflicts:
# models/issue_comment.go
* Proper date validation
* Fixed indention
* moved css to css file
* added documentation for error codes
* after merge cleanup
* Added swagger description
* DO NOTHING BUT TRIGGER THAT F*CKIN CI SO IT PICKS UP THE LATEST COMMIT AS IT SHOULD
* DO NOTHING BUT TRIGGER THAT F*CKIN CI SO IT PICKS UP THE LATEST COMMIT AS IT SHOULD
* regenerated stylesheets
Currently some issues need to be resolved and features need to be implemented before we can move the Gitea development workflow to a Gitea instance. Many ask why Gitea isn't hosted on Gitea, now that's in the FAQ.
* better commented KeywordsFound bitmask constants
* populate issueKeywordsToFind variable at point of definition rather
than in init()
* add needed `xorm:"-"` statements to the fields that were added to
Comment
* also move calculation of uniqueID out of loop
Commit features:
- renders reference comments only if their source still exists (except
for old style commit refs)
- allows for more complex rendering options, e.g. issue or commit
status, quoted comments, etc.
- properly handles updates to issue/PR titles, movement of repositories,
etc.
NOTE: Only the en_US locale is provided by this commit.
Add the LoadReference function to prepare data members of reference
types of comments for frontend rendering. Also prepares for the
transition of commit reference comments into a new message format.
The UpdateIssuesComment function is now being called when:
- a pull request is merged, so the pull request title or description can
open/close issues
- a new pull request is created, so it can reference an issue from its
title or description
- a new issue is created, so it can reference an issue from its title or
description
- a pull request or issue title or description is updated
- a comment is created or updated, so it can reference an issue from its
title or description
