gergely/calendar-social
1
0
Fork 2
Code Issues 24 Pull Requests 3 Releases Wiki Activity

[WIP] Calculate response visibility #91

Draft
gergely wants to merge 2 commits from response-visibility into master
pull from: response-visibility
merge into: gergely:master
Conversation 0 Commits 2 Files Changed 2 +348
gergely commented 2018-07-17 09:36:18 +02:00
Owner
Copy Link

This is the implementation of my original response visibility calculation (see #90). Now I truly doubt this should be the way, but it will be good as a reference.

This is the implementation of my original response visibility calculation (see #90). Now I truly doubt this should be the way, but it will be good as a reference.
gergely changed title from WIP: Calculate response visibility to [WIP] Calculate response visibility 2018-07-17 09:42:07 +02:00
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin response-visibility:response-visibility
git checkout response-visibility
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gergely
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gergely/calendar-social#91
No description provided.
Delete Branch "response-visibility"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?