gitlab-org--gitlab-foss/app/views/events/_event.html.haml

- if event.visible_to_user?(current_user)
  .event-item
    .event-item-timestamp
      #{time_ago_with_tooltip(event.created_at)}

    - if event.created_project_action?
      = render "events/event/created_project", event: event
    - elsif event.push_action?
      = render "events/event/push", event: event
    - elsif event.commented_action?
      = render "events/event/note", event: event
    - else
      = render "events/event/common", event: event
- elsif @user&.include_private_contributions?
  = render "events/event/private", event: event
Rename `Event#proper?` to `Event#visible_to_user?` 2016-03-24 13:24:22 -04:00			`- if event.visible_to_user?(current_user)`
Resolve "Redesign activity feed" 2018-11-06 09:33:42 -05:00			`.event-item`
Use css truncation on dashboard 2014-05-26 16:26:41 -04:00			`.event-item-timestamp`
Replace jQuery.timeago with timeago.js 2016-09-08 14:57:24 -04:00			`#{time_ago_with_tooltip(event.created_at)}`
Processing with note events. reformated dashboard for more events to handle 2012-12-14 14:39:55 -05:00
Rename methods that conflict in Rails 5.2 Adds suffix to enum methods and changes `in_groups` to `of_groups` 2019-05-13 00:42:06 -04:00			`- if event.created_project_action?`
Remove event caching code Flushing the events cache worked by updating a recent number of rows in the "events" table. This has the result that on PostgreSQL a lot of dead tuples are produced on a regular basis. This in turn means that PostgreSQL will spend considerable amounts of time vacuuming this table. This in turn can lead to an increase of database load. For GitLab.com we measured the impact of not using events caching and found no measurable increase in response timings. Meanwhile not flushing the events cache lead to the "events" table having no more dead tuples as now rows are only inserted into this table. As a result of this we are hereby removing events caching as it does not appear to help and only increases database load. For more information see the following comment: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037 2016-11-23 08:14:04 -05:00			`= render "events/event/created_project", event: event`
Rename methods that conflict in Rails 5.2 Adds suffix to enum methods and changes `in_groups` to `of_groups` 2019-05-13 00:42:06 -04:00			`- elsif event.push_action?`
Remove event caching code Flushing the events cache worked by updating a recent number of rows in the "events" table. This has the result that on PostgreSQL a lot of dead tuples are produced on a regular basis. This in turn means that PostgreSQL will spend considerable amounts of time vacuuming this table. This in turn can lead to an increase of database load. For GitLab.com we measured the impact of not using events caching and found no measurable increase in response timings. Meanwhile not flushing the events cache lead to the "events" table having no more dead tuples as now rows are only inserted into this table. As a result of this we are hereby removing events caching as it does not appear to help and only increases database load. For more information see the following comment: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037 2016-11-23 08:14:04 -05:00			`= render "events/event/push", event: event`
Rename methods that conflict in Rails 5.2 Adds suffix to enum methods and changes `in_groups` to `of_groups` 2019-05-13 00:42:06 -04:00			`- elsif event.commented_action?`
Remove event caching code Flushing the events cache worked by updating a recent number of rows in the "events" table. This has the result that on PostgreSQL a lot of dead tuples are produced on a regular basis. This in turn means that PostgreSQL will spend considerable amounts of time vacuuming this table. This in turn can lead to an increase of database load. For GitLab.com we measured the impact of not using events caching and found no measurable increase in response timings. Meanwhile not flushing the events cache lead to the "events" table having no more dead tuples as now rows are only inserted into this table. As a result of this we are hereby removing events caching as it does not appear to help and only increases database load. For more information see the following comment: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037 2016-11-23 08:14:04 -05:00			`= render "events/event/note", event: event`
			`- else`
			`= render "events/event/common", event: event`
Fix the group and project activity pages 2018-09-11 12:40:44 -04:00			`- elsif @user&.include_private_contributions?`
Include private contributions in user contribution graph 2018-09-07 11:08:55 -04:00			`= render "events/event/private", event: event`