GitLab Calendar

Push GitLab issue due dates to your Google Calendar or any CalDAV calendar

Create an account or Sign In

What does GitLabCalendar do?

The GitLabCalendar application creates, updates and deletes calendar events on basis of due date values in GitLab issues.
It works with Google Calendar and with any calendar that supports CalDAV, such as ownCloud, Nextcloud, mailbox.org or Fastmail.
In GitLabCalendar users can assign one of their own calendars to a project in GitLab. In a GitLab project you can create issues and add a due date value to each issue.
When a due date value in a GitLab issue gets added, changed or removed, a related event in the assigned calendar gets created, changed or removed based on the due date value. The calendar event has the GitLab issue title as its name, contains the Link to the GitLab Issue in the description field and contains the Issue "due date" as the event date.

How does GitLabCalendar work?

To grant GitLabCalendar access to your GitLab data you need to create a Personal access token at your GitLab Profile. You have to set the flag at the Scope "api Access your API"

The access token is the only thing which the Gitlabcalendar stores in your account! No Issues, no Project Data or anything else.

If you want to delete the access, you simply remove the personal access token in your gitlab account.

GitLabCalendar can write to Google Calendar and to any calendar that speaks CalDAV, for example ownCloud, Nextcloud, mailbox.org or Fastmail. You can connect both at the same time and pick per project where its issue dates should go.

To access your Google Calendar, GitLabCalendar uses OAuth 2.0 authorization to access the Google Calendar API. If you want to delete the access, you simply remove it in the permissions section of your Google account or by deleting your GitLabCalendar account.

For a CalDAV calendar, GitLabCalendar stores the address of your calendar server together with your username and an app password. The password is stored encrypted. Please use an app password rather than the password of your account, so you can withdraw access at any time without changing your own password. You can remove the access yourself under Preferences, or by deleting your GitLabCalendar account.

After you created an account you can connect one of your Calendars to one of your GitLab projects.

After you connected a Calendar to a GitLab Project, the GitLabCalendar service creates a webhook for issue events for the selected GitLab Project to get notified about Issue updates.

GitLabCalendar stores the following data:
  • Gitlab personal access token
  • Gitlab Project Id when you connect a calendar to it
  • The calendar you connected to a Gitlab Project, and which provider it belongs to
For Google Calendar:
  • Google OAuth token
For a CalDAV calendar:
  • The address of your calendar server
  • Your username on that server
  • Your app password for that server, stored encrypted

You need to have maintainer or owner permission on the Gitlab project you want to connect to a calendar.

You can connect these projects to every calendar you have write access for, on Google Calendar as well as on your CalDAV server.