@wendynather @1password Hmm this interests me on multiple levels, I may be in touch about this. My employer #gitlab is already a 1Password customer, this is quite interesting for me.
@wendynather @1password Hmm this interests me on multiple levels, I may be in touch about this. My employer #gitlab is already a 1Password customer, this is quite interesting for me.
I know this is for a car, but many a thing cried out at a command line.
Temporary migration of our projects to GitLab
We have recently started migrating our projects to GitLab as a result of GitHub not fixing our issue of GitHub Actions workflows not running due to hidden non-payment of $0. This migration allows us to not only restore our CI/CD pipelines for our builds, but it also allows us to continue making quality products as we’ve always promised you from the beginning of the year.
GitLab is an open-source software that allows you to manage your repositories for your open-source projects, and hosts various options, such as issues, pipelines, and more. Meanwhile, GitHub is a proprietary software that does the same thing, and is owned by Microsoft.
We have recently started our migration to GitLab by importing almost all repositories (archived or not) from our official GitHub account. While the main repositories get automatically updated by pushes to GitLab, our repositories that are located there don’t get updated by pushes to their GitHub counterparts. We recommend starting all pull requests in the GitLab repositories instead.
This was done in response to GitHub’s lack of support for such issues for GitHub Actions, considering the severity of the issue, and several people have faced this issue as you can see in this discussion. This is going to be temporary, while GitHub fixes this problem, which should happen soon.
All links will be updated to point to GitLab to let users know of our new (and temporary) place for our projects while a fix is incoming.
I just posted to my blog -- "Storing SSH Private Keys in GitLab CICD variables": When storing an SSH private key in GitLab CICD variables I encountered a strange error: "Unable to create masked variable because: The value cannot contain the following characters: whitespace characters." -- Read more here: https://www.dfoley.ie/blog/storing-ssh-private-keys-in-gitlab-cicd-variables -- #linux #gitlab #ssh #POSSE
So, Gitlab-Board wieder schlanker gemacht und Nutzung des Projekt-Icons als Favicon (stat des Gitlab-Icons) via Tampermonkey.
https://collaborating.tuhh.de/tobias.zeumer/Tampermonkey
Mal sehen, ob es sich bewährt.
Das ist so feist, dass meine Abteilung jetzt doch vom eher etwas rudimentären Mattermost-Kanban zum Gitlab-Issue-Management umgezogen ist.
Sehr schön auch, dass alle in der Abteilung damit einverstanden waren, dass alle aus dem Haus mit Gastrolle (erlaubt Kommentare in Tickets und Mentions) alles sehen dürfen. So eine Haltung ist nicht selbstverständlich.
Das macht so Spaß.
Upgraded my GitLab instance to version 18, running Docker
on Ubuntu server on RaspberryPi
:
1. Pull a new docker image version
2. Stop the container
3. Start the container
4. Done
Thanks #gitlab for making it this easy
So far, some organisations are differentiating themselves by having nothing to do with the #MOLE Training craze. Or developing modest, fully libre versions of the tech in-house, for a few specific features appropriate to its few strengths (eg auto-translation). When the bubble finally bursts (soon, perhaps?), these orgs will come out of it with their credibility intact.
Meanwhile those that leaned into the hype will have to rebuild theirs from scratch. Looking at you @gitlab.
And yes, whoever uses #discord for #documentation and #versioning instead of a goddam #git [doesn't have to be @github / #GitHub or @gitlab / #GitLab or @Codeberg / #Codeberg or even @gitea / #Gitea - just use any git
and write down your documentation in a useable format like #Markdown or goddamn ASCII plain text FFS] should be banned for life from #coding, working in #IT or contribute to #FLOSS.
Heh, you can add emoji into #GitLab labels.
Alright, I am giving this a try.
Checking news (i.e. social media) only once in the morning and once in the evening.
I made it through yesterday that way, even abstained from the phone on the toilet, and I am moderately proud of myself.
It is a bit hard for a #Scala programmer, because we frequently wait on builds to complete. https://xkcd.com/303/ Huge potential for distraction there. I managed to look only on browser tabs with #Jira and #Gitlab and such.
Let's see about the weekend...
me: /spend 0.14h
GitLab:
Mon client aimerait bien que je fasse la formation " GitLab CI/CD, maîtriser la gestion du cycle de vie de vos développements logiciels".
Et moi j'aimerai bien la faire à Grenoble (et les dates de la session distanciel c'est pas possible).
Pr le moment, la session de Grenoble n'est pas confirmée parce qu'on est pas assez nombreux/nombreuses. (il manque 1 personne)
Donc je jette une bouteille à la mer, si votre poste nécessite une formation Gitlab (et que votre employeur a le budget), c'est par là bas: https://www.orsys.com/fr/formation/formation-gitlab-ci-cd-gestion-du-cycle-de-vie-des-developpements-logiciels.html
Venez nous rejoindre, pr qu'on s'évite un fastidieux déplacement à Paris.
#grenoble #gitlab
So... I decided to rebase the project codebase.
The results of my work you can see here https://gitlab.com/xolatgames/birdy-wants-crisps
So as you can see - the work on the project is in full swing
But while I "rebase" the source code of the project - it can't will be running!
My self-hosted #GitLab Git server running!
Ratestunde!
Wie / in welchem Format muss die #IPv6 localhost Adresse in die #gitlab config, damit sie passend ins yaml gerendert werden kann und danach auch von da passend in die weiteren configs gerendert werden kann?
(ganz konkret gehts um den config eintrag `nginx['real_ip_trusted_addresses']`)
Hint: `::1` ist's nicht.
(1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg and so forth makes it easy to do so without creating a new account for each report.
My recommendations:
- be polite - people are spending their spare time to help you
- explain it thorough: exact steps to reproduce, difference between actual result and expected result, mention exact version numbers, surrounding environments with their versions, background stories (maybe in an extra section at the end), ...
Fun fact: many(!) of my #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.
...
Sometimes it really does help if a lot of people comment. The #ActivityPub issue was reopened by #Gitlab:
https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2603598572