forked from go-gitea/gitea
-
Notifications
You must be signed in to change notification settings - Fork 0
Add bucket storage #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
Open
masudur-rahman
wants to merge
311
commits into
master
Choose a base branch
from
add-bucket-storage
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
948fdc8 to
525629a
Compare
… form (go-gitea#6953) * Fix go-gitea#6951 - logs show proper HTTP Method, and allow change HTTP method in form * enforce POST method for webhook * set default if method is empty
* add make targets for js,css, add javascript linter - add `make js`, deprecating `make javascripts` - add `make css`, deprecating `make generate-stylesheets` and `make stylesheets-check` - changed the unclean css check to only run on CI - add JS linting via eslint with basic configuration and fixed discovered issues - changed autoprefixer to use official `postcss-cli` avoiding the need to loop in the makefile - moved browserslist to package.json so other future tools can use it too. - update documentation for new make targets and added JS section * fix indentation * move functions used in html to 'exported' list * Run lessc binary without having to install anything to node_modules * use relative paths to node bin scripts, removing npx * Revert "use relative paths to node bin scripts, removing npx" This reverts commit 119b725. * fix lessc and postcss plugins * check for node_modules and use actual bin names
Handle case where an orginization is private but a user who is not a member of the orgninization has been added as a collaborator of a repo within that org Fixes go-gitea#6962
* remove and disable package-lock Using exact versions in package.json has the same effect as lockfiles without all the troubles the lockfiles bring (different versions of package manager generating different lockfiles primarily). Ensured we only use exact versions in package.json and stopped generation of new lockfiles via .npmrc which is support by both the npm and yarn package managers. Fixes: go-gitea#6967 * enable save-exact
* Stop running hooks on pr merge * Remove SSH_ORIGINAL_COMMAND from the pushing environment
* fix index produces problem when issues/pulls deleted * fix tests * fix tests * fix tests
5331311 to
ef0bd78
Compare
* make http connections resuable * add error handler * fix lint
* Fix TestSearchRepo by waiting till indexing is done * Update integrations/repo_search_test.go * changes as per @mrsdizzie
* Fix documentation on Oauth2.Enable flag The docs list this as ENABLED, but in the source code it's ENABLE, meaning following the docs leads to confusion. * Update sample config for oauth2.ENABLE
* Change UpdateRepoIndex api to include watchers * Add timeout
Appended the Troubleshooting section with a subsection about the problems with the arm7 version and the recommendation to switch to arm6.
* Show git-notes * Make git-notes heading text localizable * Refactor git-notes data fetching to a separate function * Display the author and time of git notes * Move note bubble inside the commit bubble * Revert "Move note bubble inside the commit bubble" This reverts commit c0951fe. * Add test for git-notes * testing ui * Polish CSS * Apply suggestions from code review Co-Authored-By: Lauris BH <[email protected]>
…gitea#7017) Fixed go-gitea#6542 When creating users DefaultAllowCreateOrganization was ignored. Signed-off-by: Julian Picht <[email protected]> * fix TestCreateUser_Issue5882 Signed-off-by: Julian Picht <[email protected]>
Fixes go-gitea#6960 According to [spec][1], /verify requests must have `Accept: application/vnd.git-lfs+json` Previous code works because `git-lfs` also [violates spec and doesn't send any Accept header at all][2] For other clients that DO set `Accept: application/vnd.git-lfs+json`, addition of `Accept: application/vnd.git-lfs` either forces them to violate the spec or is ignored, depending on order in what they create header list. [1]: https://github.com/git-lfs/git-lfs/blob/master/docs/api/basic-transfers.md#verification [2]: git-lfs/git-lfs#3662
The update call on the user call races if there is more than one repository creation concurrently, leading to incorrect count of repos. Split things in two, so that we call the update for last visibility (which isn't problematic if it races, since it can only ever be best-effort anyway). This way we can atomically increment the count of repos.
…gitea#7478) * Fixes go-gitea#7474 - Handles all redirects for Web UI File CRUD * Fixes lint errors * Typo fix * Adds unit tests for a few helper functions * Fixes per review * Fix for new branch creation and to unit test * Fixes the template used for errors on delete
* Include thread related headers in issue/coment mail Make it so mail programs will group comments from an issue into the same thread by setting Message-ID on initial issue and then using In-Reply-To and References headers to reference that later on. * Add tests * more tests * fix typo
* Add branch protection information to branches page This change will add a tag on the ui that indicates whether a branch is protected on the repository branches page. Signed-off-by: Gary Kim <[email protected]> * Add last commit information to repo branches page This change adds the ID and commit message of the last commit on a branch to the branches page for repositories. Signed-off-by: Gary Kim <[email protected]> * Make branch page commit message truncate in css rather then template The truncating of commit messages shown under branches in the repository branches page has been moved to using css rather then the Go template as the template was causing some issues when the commit messaged had a link when rendered. This commit also makes the commit message paragraph itself use flex in order to make managing its elements easier. Signed-off-by: Gary Kim <[email protected]>
* Update CONTRIBUTING.md with information about DCO References: go-gitea#7389 More information: https://about.gitlab.com/handbook/marketing/community-relations/code-contributor-program/#developer-certificate-of-origin-dco * Update CONTRIBUTING.md Co-Authored-By: zeripath <[email protected]>
The default branch's name on the branches page for a repo was previously simply text and did not link anywhere. The name is now a link to the default branch just like the non-default branch names. Signed-off-by: Gary Kim <[email protected]>
* Added total count of contributions to heatmap Signed-off-by: kolaente <[email protected]> * make css Signed-off-by: kolaente <[email protected]>
* fix pr count error * fix tests
When using wiki page names that include a slash behind a Apache HTTPD reverse proxy, AllowEncodedSlashes NoDecode and appending nocanon to the ProxyPass directive is required. This commit adds that information to the documentation. Signed-off-by: Gary Kim <[email protected]>
Just makes it a bit more obvious which values we want to test for, and which ones we want to ignore.
No need to wrap this.
Don't assign values we never use.
* Fix empty commits now showing in repo overview * add test * make fmt
ef0bd78 to
217a785
Compare
217a785 to
6f47a3b
Compare
6f47a3b to
320cf21
Compare
…vendor` Signed-off-by: Tamal Saha <[email protected]>
320cf21 to
0728562
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AvatarfromBucket(Google, Azure and S3)Avatarfrom local storageTo store
Avataron bucket the following code must be onapp.inifile. Ifapp.inidoesn't contain the following section, the avatar will be stored on local storage.The
Bucketmust be public.