summaryrefslogtreecommitdiffstats
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Bugfix: when changing project ownership to a group, give admin rights to all ↵HEADorigin/masterorigin/HEADmasterMarius Mathiesen2010-02-181-2/+8
| | | | | | mainline repositories Until now, committerships created for these repositories would have a nil permissions mask.
* Fix a bug where Gitorious would try to notify about commit events to watchers.Marius Mathiesen2010-02-181-0/+11
| | | | Only push events should fire notifications.
* Adding a counter of pushes since last garbage collection, incremented when ↵Marius Mathiesen2010-02-031-5/+42
| | | | | | | | pushed to and reset when gc-ed The algorithm for finding gc candidates is unchanged, will run this in production and collect metrics for changing this the next few days. - Also tracking disk usage for repositories, calculated when pushed to and stored in the database
* Process messages for merge request version branch deletionMarius Mathiesen2010-02-012-2/+91
| | | | - Use tracking repository instead of target repository, since this is where the tracking branches are kept
* Send a message to MQ when a MergeRequestVersion is deleted in order for a ↵Marius Mathiesen2010-02-011-0/+27
| | | | processor to delete the tracking branch.
* Adding JSON support to Blobs#historyMarius Mathiesen2010-01-261-0/+8
| | | | This was requested on IRC the other day, to check for updates to a Greasemonkey script
* Allow user to have new favorites by default fire notificationsMarius Mathiesen2010-01-261-0/+18
|
* Fix missing event rendering for merge request; fixes a bug when updating ↵Marius Mathiesen2010-01-261-1/+19
| | | | merge requests
* Destroy events for favorites when favorites are destroyed.Marius Mathiesen2010-01-211-9/+17
| | | | Rendering events lacking its target fails
* Make sure the FeedITems for a given Event is destroyed along with the eventJohan Sørensen2010-01-151-0/+2
|
* Make push event notifications (email) display display the correct number of ↵Marius Mathiesen2010-01-151-0/+5
| | | | | | | commits in push. Since the commit events are created after the push, we need to save the commit events first, then send notifications. Event#disable_notifications handles this, the processor uses and explicitly sends notifications afterwards.
* Add a dashboard breadcrumbJohan Sørensen2010-01-121-0/+6
|
* Renamed /activity route to /activitiesJohan Sørensen2010-01-121-15/+15
|
* Introducing Site#public_timeline as /activityMarius Mathiesen2010-01-121-0/+15
| | | | The global activity stream is now available for logged in users too
* Changed it to logged in users will be displayed their dashboard on /Marius Mathiesen2010-01-121-4/+40
| | | | - Anonymous users will be served one of the two public start pages, depending on gitorious_dot_org being true or false
* Deliver an email for each watchable event, if it's turned on for the given ↵Johan Sørensen2010-01-113-0/+62
| | | | favorite
* Fixed a couple of FavoritesControllerTest pending testsJohan Sørensen2010-01-071-6/+10
|
* Support for plaintext rendering of eventsJohan Sørensen2010-01-071-0/+374
| | | | | | | The EventRendering::Text class is responsible for rendering plaintext versions of events, this makes it easier to test and maintain than. Hopefully we can one day move the html rendering of events into a EventRendering::HTML module.
* Added a UI for managing whether to receive email when a feed item appears or notJohan Sørensen2010-01-071-2/+63
| | | | Flagging this is a per favorite setting and is opt-in
* Support for watching a merge request version through commenting.Marius Mathiesen2009-12-151-9/+24
| | | | Also (finally) added support for login_as(<User>)
* Make it possible to start watching a merge request when submitting a comment ↵Marius Mathiesen2009-12-151-0/+31
| | | | | | on it. Currently only for non-inline comments, this is up next
* Project#search_repositories now uses the same logic as Repository#search_clonesMarius Mathiesen2009-12-141-6/+6
|
* Perform Repository#search_clones in SQL instead of RubyMarius Mathiesen2009-12-142-1/+64
|
* Fix live search test in IEJohan Sørensen2009-12-141-6/+6
| | | | | The fixture HTML was nested improperly, causing IE to fail in its usual fashion
* Added another field - last_activity_at - to messages, used in sorting ↵Marius Mathiesen2009-12-101-6/+15
| | | | | | | messages for a user. This field is updated independently of other actions on a thread. On new records it is the current time, when a reply is created, this is set to current time.
* Do not create favorites for new repositories if it's an internal kind of repoJohan Sørensen2009-12-101-7/+17
|
* Creating a project adds the creator as a watcher of eventsJohan Sørensen2009-12-101-40/+46
|
* Add repository user as a watcher when creating a new repositoryJohan Sørensen2009-12-102-1/+11
|
* Move creation of favorites into controller. Also adding merge request to ↵Marius Mathiesen2009-12-102-10/+9
| | | | owner's favorites upon creation
* Don't attempt to create a committership delete event when deleting a userJohan Sørensen2009-12-101-0/+10
|
* Change the way reviewers are notified about new merge requestsMarius Mathiesen2009-12-101-13/+19
| | | | | | | | | | When a merge request is created, each reviewer has this added as a favorite. In the same process, a FeedItem is created for the event associated (now created in the model and accessible as #creation_event). Messages are no longer sent to the reviewers, as this gave a lot of email to the reviewers. Instead, they will now be able to track the creation (and updates) of merge requests through their newsfeed. Since notifications are no longer sent to reviewers, the checkbox on Repositories#edit is no longer displayed (it has no effect). It is still in the database, though.
* Formatting cleanupJohan Sørensen2009-12-101-5/+5
|
* Don't create feed items for users who are the creator of an eventJohan Sørensen2009-12-102-7/+26
| | | | | Users wouldn't be too interested in getting notified about what they just did
* Don't create FeedItems for commit events and fetch 30 events for the ↵Johan Sørensen2009-12-091-0/+9
| | | | newsfeed atom feed
* Create a FeedItem model for the User which is responsible for populating his ↵Johan Sørensen2009-12-094-9/+43
| | | | | | | | | | | | | | | newsfeed The FeedItem is a simple pseudo-join model between a User and the Events he needs to see in his newsfeed. By having it in a seperate table we can use it as an index of sorts to figure out which events he needs to see. The FeedItems are populated in a bulk manner after an Event is created by figuring out who watches (through Favorite) the object the Event belong to. The FeedItem not only makes the finding of watched events faster, it also allows us to insert things into the event that we cannot do through a straight join between favorites and events.
* When a merge request is created (confirmed_by_user), each reviewer will have ↵Marius Mathiesen2009-12-092-0/+41
| | | | | | a favorite created. - Support creation of favorites without creating an event.
* Display a summary of the user's messages on ~usernameMarius Mathiesen2009-12-091-0/+16
| | | | Only when the current user is accessing the page, of course
* Don't do a heavy count() query when paginating the ~user newsfeed, instead ↵Johan Sørensen2009-12-082-8/+8
| | | | | | cheat. .. by always assuming there's one more record than what's displayed on the page
* Touch the root message when a reply is created, sort user#messages_in_inbox ↵Marius Mathiesen2009-12-081-0/+17
| | | | by updated_at
* Only create an event the first time a user starts watching somethingMarius Mathiesen2009-12-081-0/+11
|
* Make the javascripts powering favorite_button work with several elements on ↵Marius Mathiesen2009-12-081-14/+14
| | | | | | the page The jQuery extension now calls a function on each element matched by the selector
* Make sure that we can remove a repository's descriptionJohan Sørensen2009-12-082-0/+17
| | | | | Make Repository#replace_value accept an allow_blank parameter to control whether blank values are ok or not.
* Adding an Atom feed for user's watchlistMarius Mathiesen2009-12-071-0/+9
| | | | - An additional link... tag in Users#show
* Projects can be favorited too (no link in the GUI yet, but still)Marius Mathiesen2009-12-072-0/+41
|
* Make merge requests watchableMarius Mathiesen2009-12-071-0/+19
| | | | | - Moved linking logic into FavoritesHelper - Favorites know of their project
* Do not use Ajax for loading events, deleting now obsolete codeMarius Mathiesen2009-12-071-26/+0
|
* Fixed 1.8 syntax error in UserTestJohan Sørensen2009-12-071-81/+83
|
* Include user favorites in Users#showMarius Mathiesen2009-12-031-0/+26
| | | | - Let the user toggle between his own activities and what he's watching on his own page
* Add an event when someone starts watching a repository.Marius Mathiesen2009-12-031-0/+15
| | | | - Added rendering of favorite related events
* Favorites: GUI improvements, rename user accessor to eventsMarius Mathiesen2009-12-032-5/+28
| | | | | - Added waiting indicator when favoriting, added CSS classes - Renamed User#favorite_events -> User#events_in_watchlist
* Access to a user's favorite eventsMarius Mathiesen2009-12-032-6/+35
| | | | Removed old copyrights.
* Giving test coverage to link helperMarius Mathiesen2009-12-031-7/+42
|
* Moving the form replacer into a testable jQuery pluginMarius Mathiesen2009-12-031-0/+30
|
* Hook into the create/delete actions for watching with some Ajax goodnessMarius Mathiesen2009-12-031-2/+15
| | | | | | - Add a custom attr to the a tags - Replace the obtrusive Rails actions with some homebrew - Favorites#{create,destroy} now supplies a Location header intercepted by javascript
* Adding Favorites#destroy, set flash, add link to (un)favorite repositoryMarius Mathiesen2009-12-031-0/+31
|
* FavoritesController: provides watching of repositoriesMarius Mathiesen2009-12-033-0/+109
| | | | - Also added Copyright header where missing
* Improve the favorite/favoritable model:Marius Mathiesen2009-12-032-3/+25
| | | | | - Validations - Extract watchable logic into module
* Adding basic favorite modelMarius Mathiesen2009-12-032-0/+27
|
* Only include groups user is an admin for list of teams a user can transfer a ↵Johan Sørensen2009-12-031-89/+98
| | | | project to
* Add a footer to the notification_copy email that you shouldn't reply via emailJohan Sørensen2009-12-021-1/+1
|
* Add a tally of merge requests the user may wish to look at on his ~user pageJohan Sørensen2009-12-011-55/+48
| | | | Also try out some restructuring of the ~user page
* attr_protect Committership#permisssions from mass attribute updatesJohan Sørensen2009-11-304-43/+33
| | | | | | Also ad a Committership::create_with_permission to easy expressing things, mostly for usable for test and utility code NOT for controller code.
* Don't just assume committership when deciding when to show the "request ↵Johan Sørensen2009-11-302-2/+14
| | | | | | | merge" link Requesting a merge from one mainline to another doens't make sense, since they don't have any parents
* Fixed 1.8 syntax error in the MergeRequestProcessorTestJohan Sørensen2009-11-301-9/+8
|
* Removing obsolete, commented codeMarius Mathiesen2009-11-301-14/+0
|
* Of course, the MergeRequestProcessor needs and expects Merge requests by id, ↵Marius Mathiesen2009-11-301-3/+3
| | | | not sequence number
* Load the correct merge request in various scenariosMarius Mathiesen2009-11-302-14/+2
| | | | | | | - Repositories#config scopes merge requests on repository - MergeRequestProcessor looks up by sequence number, not id - PushEventProcessor finds merge request in repo, not directly by sequence_number - MergeRequests#show use to_param in title
* MergeRequest's to_param now uses the sequence number instead of idMarius Mathiesen2009-11-305-31/+48
| | | | | | | | | | A summary of what's changed: - Routing - Links, where necessary - Git branch names use seq instead of id Also made some refactorings in PushEventProcessor to make it testable without a full stack test. And set some revealing sequence numbers in the fixtures.
* Adding an index for sequence numbers in merge requestMarius Mathiesen2009-11-301-1/+1
|
* Avoiding ridiculously high sequence numbersMarius Mathiesen2009-11-302-7/+31
| | | | | - Try to represent the # of merge requests in a repo in the sequence number - If this sequence is taken, build on the highest existing one until this is surpassed
* Merge request sequences should be unique for each target repositoryMarius Mathiesen2009-11-301-2/+15
|
* Adding sequence number to merge requests, will replace id in URLs etc.Marius Mathiesen2009-11-303-5/+51
|
* Make it more obvious that the new message notifications are just thatJohan Sørensen2009-11-301-7/+8
| | | | | The outgoing email notification when receiving a private message should be a lot clearer that it is a message
* Don't rely on hash sort orderingJohan Sørensen2009-11-271-1/+1
|
* Don't blow up if Committership#build_permissions receives nilJohan Sørensen2009-11-261-0/+5
|
* Make sure the Comment tests relating to notifications start on a clean slateJohan Sørensen2009-11-261-0/+1
|
* Be able to edit permissions on a committershipJohan Sørensen2009-11-261-0/+31
|
* Remove the "repo can't be deleted if it's the last mainline" checkJohan Sørensen2009-11-241-7/+0
| | | | In practice its function is a bit counter-intuitive and not really useful
* Use Repository#admin? instead if repo.owner.admin? to query for adminshipJohan Sørensen2009-11-243-58/+92
| | | | | That way we use the collaborator permissions instead of just the owner, which is inline with how the new permission scheme works
* Added Repository#{admin,reviewer,committer}? helpers and fixup ↵Johan Sørensen2009-11-241-8/+68
| | | | | | can_be_deleted_by? The can_be_deleted_by? method now takes the proper adminship (through the committerships) into account
* Add sanity-check assertionJohan Sørensen2009-11-241-0/+1
|
* Use "Collaborator" instead of "Committer" when adding new committershipsJohan Sørensen2009-11-191-17/+17
| | | | | The Committership class really needs a different name now that they have more fine-grained permissions, but now just change the UI.
* Only notify reviewers about new merge requestsJohan Sørensen2009-11-191-68/+72
|
* Add controller+view code for setting permissions on a CommittershipJohan Sørensen2009-11-192-2/+11
|
* Fixed failing RepositoriesControllerTest (didn't set the review bit)Johan Sørensen2009-11-191-185/+188
|
* MergeRequest#resolvable_by? should use the committerships with a review bitJohan Sørensen2009-11-192-1/+13
|
* Repository#committers should only include users from committerships with ↵Johan Sørensen2009-11-192-7/+30
| | | | commit bit
* Be able to get a list of permissions out of a CommittershipJohan Sørensen2009-11-191-0/+5
|
* Create the proper initial Committership permissions when a repository is createdJohan Sørensen2009-11-192-1/+12
|
* Added auxiliary methods on Committership for checking and fetching based on ↵Johan Sørensen2009-11-191-1/+52
| | | | permission masks
* Add a permissions bitmask to CommittershipJohan Sørensen2009-11-191-18/+42
|
* Make sure MergeRequestVersion comment notifications says its for a merge requestJohan Sørensen2009-11-191-9/+30
|
* re-activate tree commit cachingJohan Sørensen2009-11-171-139/+139
| | | | and trim excess whitespace
* Specify whether a repository accepts merge requestsMarius Mathiesen2009-11-173-0/+59
| | | | | | - On by default - Inherits the value from its parent when cloned - When set to off: do not include in targets for merges, do not display link to merge requests on Repository#show
* Enable clicking a comment to jump to the inline context.Marius Mathiesen2009-11-161-3/+1
| | | | - Also got back support for side by side rendering of diffs
* Render the new comment and diffs when inline commenting on a commitMarius Mathiesen2009-11-161-0/+3
| | | | - Made partials/javascripts reusable between different inline commenting objects
* Make Comments#create render something meaningful when receiving a comment on ↵Marius Mathiesen2009-11-162-0/+39
| | | | | | a commit - A minor refactoring of this whole rendering was indeed required
* Mark the whole message thread as read by the recipient when he reads itJohan Sørensen2009-11-161-0/+20
|
* Some UX tweaks to the live search functionMarius Mathiesen2009-11-161-0/+28
| | | | | - Performing an empty search resets the search form (no search, just display standard contents) - When no matches are found, render a div with class no-results-found (if any)
* Extract some stuff from the MessagesController into the modelJohan Sørensen2009-11-161-1/+21
|
generated by cgit v1.1 at 2025-05-12 20:16:10 +0000