dnsmichi

12 ms·

1. 61.▲
   by dnsmichi 4y ago

   GitLab team member here. Sharing a personal insight - I'm currently moving flats in the Nuremberg area in Germany which is a little hectic because forced out by the new house flat owner. Async work enables me to take calls and go shopp
2. 62.▲
   by dnsmichi 4y ago

   GitLab team member here. You can make suggestions to move features between tiers, i.e. moving a paid feature to the free tier, by opening an issue following https://about.gitlab.com/company/pricing/#changing-tiers-
3. 63.▲
   by dnsmichi 4y ago

   GitLab team member here. > it would be nice if there was an option for a group-level Readme on Gitlab. Thanks for the idea. The proposal for Group READMEs is discussed in this thread: https://gitlab.com/gitlab-org/gi
4. 64.▲
   by dnsmichi 4y ago

   Thanks, great idea. Added a comment into the feature proposal in https://gitlab.com/gitlab-org/gitlab/-/issues/273250#note_11... - suggest upvoting and/or subscribing to notifications.
5. 65.▲
   by dnsmichi 4y ago

   Today I learned, thanks a lot! Created a MR for the Developer Evangelism Hacker News handbook to add this formatting tip, and some more https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...
6. 66.▲
   by dnsmichi 4y ago

   Thanks for sharing your ideas, appreciate the thoughts to learn new perspectives :-) And also thanks for contributing, every contribution counts and helps :-) Maybe see you at a future hackathon :) https://about.gitlab.com/c
7. 67.▲
   by dnsmichi 4y ago

   True, thanks. Some workflows can require larger merge requests, having the platforms and tools that enable smaller iterations help reduce (or eliminate) them though.
8. 68.▲
   by dnsmichi 4y ago

   You are more brave than I am - I have it explicitly disabled :-) https://gitlab.com/dnsmichi/dotfiles/-/blob/main/.gitconfig When I pull and it runs into a merge conflict, I want to see that error&
9. 69.▲
   by dnsmichi 4y ago

   After reading this comment about "git push --force-with-lease" in https://stackoverflow.com/a/53011907/1821348 my workflows with "git fetch" first would not work with "git push --force-wit
10. 70.▲
    by dnsmichi 4y ago

    GitLab team member here, putting my personal hat on - from my experience in using different Git workflows since 2009, a smaller clean unit of work can help with debugging and troubleshooting. It also provides a way to new team members and c
11. 71.▲
    by dnsmichi 4y ago

    Depending on the workflow and collaboration in branches in teams, amending may not be ideal. Amending changes to an existing commit will generate a new sha checksum, thus resulting in a diverging history if the branch is often pushed to the
12. 72.▲
    by dnsmichi 4y ago

    GitLab team member here. You can use `git rebase` to perform the so-called "squash" action, that squashes multiple commits at once. For example, the latest commits in the branch look like this: 123 WIP1 456 WIP2 789 WIP3 012 Featu
13. 73.▲
    by dnsmichi 4y ago

    GitLab team member here. Thanks for sharing, I have posted the project in the forum topic collecting artifact cleanup resources [0] If you need a way to generate lots of artifacts for testing your script, you might find this small CI config
14. 74.▲
    by dnsmichi 4y ago

    > The instructions for removing the most recent artifacts also just never works ( https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#k... ) What's the error / job logs you are seeing with h
15. 75.▲
    by dnsmichi 4y ago

    > What does this cover? https://about.gitlab.com/pricing/faq-efficient-free-tier/#ma... provides a list of what counts towards the storage limits, and also ways to manage, reduce and cleanup storage. > Does
16. 76.▲
    by dnsmichi 4y ago

    GitLab team member here. It seems related to the problem that you cannot open an empty PR https://stackoverflow.com/questions/46577500/why-cant-i-crea... and force overriding an old branch base is a workaround to
17. 77.▲
    by dnsmichi 4y ago

    GitLab team member here, thanks for sharing! You can also set Git push options understood by the GitLab server to create merge requests [0] on the CLI. Sid's dotfiles provide an example in [1]. The workflow is 1) push 2) create merge r
18. 78.▲
    by dnsmichi 4y ago

    Thanks for your feedback. I’d suggest starting the analysis to identify the type of most storage being consumed. Maybe CI/CD job artifacts are kept forever and need an expiration configuration [0], or container images in the registry w
19. 79.▲
    by dnsmichi 4y ago

    Thanks for sharing for your feedback. I have added more insights into caching and checkout strategies to reduce traffic and speed up job execution in GitLab Runners in this comment: https://news.ycombinator.com/item?id=32408
20. 80.▲
    by dnsmichi 4y ago

    Thanks for the suggestion of adding a Git cache for a GitLab Runner. A similar mechanism already exists that allows control of the Git strategy with fetch on a local working copy which is faster, and clone if not yet existing. All benefits
21. 81.▲
    by dnsmichi 4y ago

    > erhaps now is a good time to recommend the ever-popular BFG to anyone unaware: https://rtyley.github.io/bfg-repo-cleaner/ Thanks for sharing this tool to help cleanup the Git history. Please be aware that it will
22. 82.▲
    by dnsmichi 4y ago

    GitLab offers ways to manage retention policies for your container registry. Please see the docs for guidance: https://docs.gitlab.com/ee/user/packages/container_registry/...
23. 83.▲
    by dnsmichi 4y ago

    > And, I'm not sure if GL is counting the whole history, or the current? And are they pruning old after a certain date? GitLab stores the Git history with all data revisions as commits. To reduce the repository storage [0], older Gi
24. 84.▲
    by dnsmichi 4y ago

    GitLab team member here. Maybe you can re-use the script I shared in this comment [0] to query the GitLab REST API to generate an index. I'm a fan of using the API programmatically, and tend to avoid git checkout/grep/etc. in
25. 85.▲
    by dnsmichi 4y ago

    Thanks for flagging. opsindev.news is hosted on GitLab Pages using Let's Encrypt. Maybe the TLS ciphers or versions do not match. Which error message do you see, browser/OS and location may help (if you want to share) If the MkDoc
26. 86.▲
    by dnsmichi 4y ago

    GitLab team member here, thanks for sharing your experience! The UX with editing the wiki, using WYSIWYG content editor [0] has been improved in recent releases. [1] I peeked into 15.2 (self-managed release coming on Friday, July 22) which
27. 87.▲
    by dnsmichi 4y ago

    GitLab team member here, thanks for sharing! I'm using the Web IDE to take notes in most of my projects, work and personal, and publish the notes with MkDocs and GitLab Pages to a searchable frontend/domain when needed. Editing al
28. 88.▲
    by dnsmichi 4y ago

    Wonderful, thanks for letting us know, appreciate your collaboration and patience in resolving the problem. :)
29. 89.▲
    by dnsmichi 4y ago

    Thanks for opening the ticket already :-) I have talked with the fulfillment team at GitLab [0], and there was a problem identified with workers not syncing the purchased CI minutes after the DB migration. Corrections have been made, and po
30. 90.▲
    by dnsmichi 4y ago

    GitLab team member here. Thanks for asking - I have forwarded your question; sharing a summary what I learned below. Note that I am not a Rails engineer; for deeper questions I'd suggest commenting into the linked issues and tag engine