BigW Consortium Gitlab
Create a "destroyed Milestone" event and keep Milestone events around in the DB for posterity Also fix issue where destroying a Milestone would cause odd, transient messages like "created milestone" or "imported milestone". Now if a milestone is destroyed, at least it will indicate in the activity feed even if it's not clear which milestone was destroyed: ![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/c89cc8a0a9fa549deac433f17b890913/image.png) Closes #2382 See merge request !1227
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
admin | Loading commit data... | |
ci | Loading commit data... | |
groups | Loading commit data... | |
import | Loading commit data... | |
profiles | Loading commit data... | |
projects | Loading commit data... | |
application_controller_spec.rb | Loading commit data... | |
autocomplete_controller_spec.rb | Loading commit data... | |
blame_controller_spec.rb | Loading commit data... | |
blob_controller_spec.rb | Loading commit data... | |
branches_controller_spec.rb | Loading commit data... | |
commit_controller_spec.rb | Loading commit data... | |
commits_controller_spec.rb | Loading commit data... | |
help_controller_spec.rb | Loading commit data... | |
namespaces_controller_spec.rb | Loading commit data... | |
profile_keys_controller_spec.rb | Loading commit data... | |
projects_controller_spec.rb | Loading commit data... | |
root_controller_spec.rb | Loading commit data... | |
uploads_controller_spec.rb | Loading commit data... | |
users_controller_spec.rb | Loading commit data... |