Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
5a5cef53
Commit
5a5cef53
authored
3 years ago
by
Dustin Eckhardt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix broken spec for private events being included in the calendar
parent
6c981fe6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
spec/lib/gitlab/contributions_calendar_spec.rb
spec/lib/gitlab/contributions_calendar_spec.rb
+3
-3
No files found.
spec/lib/gitlab/contributions_calendar_spec.rb
View file @
5a5cef53
...
...
@@ -67,12 +67,12 @@ RSpec.describe Gitlab::ContributionsCalendar do
context
"when the user has opted-in for private contributions"
do
it
"shows private and public events to all users"
do
use
r
.
update_column
(
:include_private_contributions
,
true
)
contributo
r
.
update_column
(
:include_private_contributions
,
true
)
create_event
(
private_project
,
today
)
create_event
(
public_project
,
today
)
expect
(
calendar
.
activity_dates
[
today
]).
to
eq
(
1
)
expect
(
calendar
(
user
).
activity_dates
[
today
]).
to
eq
(
1
)
expect
(
calendar
.
activity_dates
[
today
]).
to
eq
(
2
)
expect
(
calendar
(
user
).
activity_dates
[
today
]).
to
eq
(
2
)
expect
(
calendar
(
contributor
).
activity_dates
[
today
]).
to
eq
(
2
)
end
end
...
...
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment