Snippets Groups Projects

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Switch to https in requirements.txt

It's annoying for external users otherwise.

Child items

0

Show labels

No child items are currently assigned. Use child items to break down this issue into smaller parts.

1

When this merge request is accepted, this issue will be closed automatically.

Activity

Daniel Bauer @he66coqe · 7 months ago

Maintainer

Related: 344b7455.

Nils Kohl @kohl · 7 months ago

Author Maintainer

@pponkumar was there a specific reason for that?

Ponsuganth Ilangovan Ponkumar Ilango @pponkumar · 7 months ago

Developer

Well, I thought that was the standard we follow or something.

I would be happy to switch to https as it is very easy

Please register or sign in to reply
Marcus Mohr created branch mohr/5-switch-to-https-in-requirements-txt to address this issue 4 weeks ago

created branch mohr/5-switch-to-https-in-requirements-txt to address this issue
Marcus Mohr mentioned in merge request !22 (merged) 4 weeks ago

mentioned in merge request !22 (merged)
Marcus Mohr mentioned in commit b215cb29 3 weeks ago

mentioned in commit b215cb29
Marcus Mohr closed via merge request !22 (merged) 3 weeks ago

closed via merge request !22 (merged)

Please register or sign in to reply

Labels

None

Milestone

None

Due date

None

Confidentiality

Not confidential

0 Participants