# bitbucket Published articles for bitbucket. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Announcing Bitbucket support for Sites and Functions DevFeed: [Announcing Bitbucket support for Sites and Functions]() Original publisher: [Read original article]() Author: Harsh Mahajan Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [bitbucket](), [Appwrite](), [Deployment](), [Git]() Tags: [announcements](), [atlassian](), [bitbucket](), [build](), [deployment](), [git](), [oauth](), [pull-request](), [qr-code]() ### AI overview Appwrite announces Bitbucket support for Sites and Functions. Users can connect a Bitbucket workspace and repository so pushes trigger builds and deployments, with branch previews, Bitbucket links, commit statuses, pull request comments, logs, preview URLs, and QR codes. ### Source excerpt Appwrite now deploys from Bitbucket. Connect a workspace, pick a repository, and every push builds a Site or Function, with links that resolve to Bitbucket. ## Troubleshoot and secure your code faster with Datadog's Bitbucket Cloud Source Code integration DevFeed: [Troubleshoot and secure your code faster with Datadog's Bitbucket Cloud Source Code integration]() Original publisher: [Read original article]() Author: Eric Metaj; Mark Azer Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Developer Tools](), [iac-security](), [Vulnerabilities]() Tags: [apm](), [bitbucket](), [ci-visibility](), [cloud](), [code](), [code-profiling](), [code-security](), [devsecops](), [error-tracking](), [infrastructure-as-code](), [integration](), [observability](), [open-source](), [pull-requests](), [secret-scanning](), [security](), [software-delivery](), [test-optimization](), [vulnerabilities]() ### AI overview Datadog's Bitbucket Cloud Source Code integration links selected repositories with Datadog so teams can investigate production issues with source context and review security findings before merging code. ### Source excerpt Connect Bitbucket Cloud to Datadog to troubleshoot with source code in context and surface test, quality, and security feedback in pull requests. ## Best Bitbucket Alternatives in 2026 DevFeed: [Best Bitbucket Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-29T11:54:28Z Content type: comparison Language: en Sources: [Semaphore Engineering]() Topics: [bitbucket](), [CI/CD](), [GitHub Actions](), [GitLab](), [Self-hosted](), [Cloud](), [Deployment](), [DevSecOps]() Tags: [2026](), [alternatives](), [bitbucket](), [ci-cd](), [circleci](), [cloud](), [compare](), [github](), [github-actions](), [gitlab](), [gitlab-ci](), [linux](), [macos](), [pipelines](), [self-hosted]() ### AI overview This comparison guide examines Bitbucket Pipelines and four alternatives--Semaphore, GitHub Actions, GitLab CI/CD, and CircleCI--to help teams choose a CI/CD platform based on source-control ecosystem, visibility, deployment control, hosting model, and operational requirements. ### Source excerpt Bitbucket Pipelines is a logical starting point for teams already using Bitbucket Cloud. It is built into the source-control experience, configured in a bitbucket-pipelines.yml file, and offers both Atlassian-hosted execution and self-hosted runners. But convenience at the repository level is not always the same thing as the best long-term CI/CD operating model. Teams evaluating Bitbucket [...] The post Best Bitbucket Alternatives in 2026 appeared first on Semaphore. ## Sign in to Pulumi Cloud with Passkeys DevFeed: [Sign in to Pulumi Cloud with Passkeys]() Original publisher: [Read original article]() Author: Devon Grove Published: 2026-07-13T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Passkeys](), [WebAuthn](), [Security](), [passwords]() Tags: [bitbucket](), [features](), [gitlab](), [google](), [oauth](), [passwords](), [product](), [product-launches](), [security]() ### AI overview Pulumi Cloud now supports passkeys for users who sign in with an email address and password. Passkeys use device-stored public-key credentials and WebAuthn, while identity-provider sign-in flows remain unchanged. ### Source excerpt Pulumi Cloud now supports passkeys for users who sign in with email and password. Select a button, approve with Touch ID, Face ID, Windows Hello, or your hardware key, and you're signed in. A passkey is a public-key credential stored on your device: your phone, your laptop, a hardware key (YubiKey, Google Titan, etc.), or your password manager can all function as the authenticator. When you sign in, your device authenticates you locally and signs a challenge from Pulumi Cloud with the private key. The private key stays on your device -- Pulumi Cloud never sees or stores it. Passkeys are built on the WebAuthn standard, so they're already supported on every major browser and operating system. Who this is for This release applies to users who sign in to Pulumi Cloud with an email address and password. If you sign in through an identity provider (IdP), such as GitHub OAuth, GitLab, Bitbucket, Google, or your organization's SAML SSO, your existing flow is unchanged. Why passkeys Passwords have always been the weakest link in account security. Since they are shared secrets, they are vulnerable to phishing attacks, and every place you type one is a place that can be impersonated or a data store that can be leaked. Passkeys swap that out for a per-site key pair that lives on your device: Phishing-resistant by design. A passkey is bound to the exact origin it was registered for. A look-alike domain can't trigger your authenticator. Synced across your devices. Apple iCloud Keychain, Google Password Manager, 1Password, Dashlane, Bitwarden: most credential managers now sync passkeys end-to-end-encrypted to every device you've signed in on. Discoverable. Pulumi Cloud doesn't need to know which user you are before you authenticate. Just select "Sign in with a passkey" and your device offers the right credential. Nothing to remember. A passkey lives on your device. There's no string to memorize, and no sensitive credential stored by us. Setting up a passkey The next time you sign i ## Trigger Deployments on Git Tags DevFeed: [Trigger Deployments on Git Tags]() Original publisher: [Read original article]() Author: Michael Fallihee Published: 2026-06-05T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Deployment](), [Git](), [releases](), [ci](), [REST API](), [GitHub]() Tags: [announcements](), [azure](), [bitbucket](), [deployment](), [devops](), [features](), [git](), [git-tags](), [github](), [gitlab](), [product](), [pulumi-cloud](), [rest](), [rest-api](), [version-control]() ### AI overview Pulumi Deployments can now trigger stack deployments when matching Git tags are pushed. Teams can enable tag-based triggers, configure glob filters, and use the tag name in deployment commands or Pulumi programs. The feature works with GitHub, GitLab, Bitbucket, Azure DevOps, and Custom VCS integrations. ### Source excerpt A git tag is how many teams mark a release as ready. Pulumi Deployments can now act on that signal directly: configure a tag-based trigger, push a version tag like v1.2.0, and Pulumi automatically runs pulumi up for your stack. No extra pipeline glue, no manual click -- your release tag is the deployment. Why tags? Push to Deploy has long let you preview changes on a pull request and update a stack when commits merge to a branch. That branch-based model is a great fit for continuous delivery to shared development and QA environments, where every merge should flow straight through. But promotion to production is often deliberate, not continuous. You merge throughout the day, then decide -- separately -- that a particular commit is the release. The conventional way to record that decision is a git tag: v1.2.0, 2026.06.0, release-2026-06-04. Tagging is already part of most teams' release rituals. Tag-based triggers connect that ritual to your infrastructure. Instead of wiring up a separate CI job to call the Pulumi Deployments REST API on a tag event, you configure the trigger once in your stack's deployment settings and let Pulumi handle the rest. How it works Tag triggers are controlled by two settings on your stack's deployment configuration: Run updates for pushed tags -- a toggle that enables running pulumi up when a matching tag is pushed. Tag filters -- a list of glob patterns that decide which tag names qualify. Tag filters use the same model as the path filters you may already know, except the patterns match against the tag name rather than changed file paths. A few examples: v* -- deploy on any tag beginning with v, such as v1.0.0 and v2.3.1. v* plus !*-rc* -- deploy on release tags but skip release candidates like v1.2.0-rc1. 2026.* -- deploy on calendar-versioned releases such as 2026.06.0. Filters prefixed with ! are exclusions, and an exclusion always wins over an include. With no filters configured and the toggle on, every tag push deploys. Deleting a tag never ## Laravel Cloud Pre-Check: Is Your App Ready to Deploy? DevFeed: [Laravel Cloud Pre-Check: Is Your App Ready to Deploy?]() Original publisher: [Read original article]() Author: Dave Hicking Published: 2026-04-24T10:00:16Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [migration](), [Cloud](), [PHP](), [Code](), [configuration](), [GitHub](), [bitbucket]() Tags: [bitbucket](), [cloud](), [code](), [docs](), [laravel](), [migration](), [php](), [pull-request]() ### AI overview This article introduces the free Laravel Cloud Pre-Check, a static analysis tool that evaluates whether a Laravel application is ready to deploy on Laravel Cloud. Developers connect a GitHub, Bitbucket, or GitLab repository and receive an actionable compatibility report as a pull request, covering requirements such as framework and PHP versions, PHP extensions, and Laravel Octane configuration. ### Source excerpt Run the free Laravel Cloud Pre-Check to get an instant compatibility report for your app. Find out what to fix before you migrate in just a few minutes. ## Using a Bitbucket Dashboard Game to Improve Pull Request Reviews DevFeed: [Using a Bitbucket Dashboard Game to Improve Pull Request Reviews]() Original publisher: [Read original article]() Author: Tom Published: 2026-04-19T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [pull-requests](), [bitbucket](), [DevOps](), [App](), [Web]() Tags: [api](), [best-practices](), [bitbucket](), [blameless-culture](), [developer](), [devops](), [gamification](), [html](), [kanban](), [people](), [pr-reviews](), [productivity](), [pull-requests](), [review](), [software-engineering](), [team](), [team-culture](), [web]() ### AI overview A team struggled with delayed pull request reviews that blocked colleagues and caused work to drift between sprints. They built a Bitbucket-based dashboard that ranked developers by outstanding reviews and displayed it on a shared TV, using humor and social pressure to encourage the team to review pull requests before standup. ### Source excerpt A story of how a team used "The Wall of Shame" to turn a bottlenecked PR review process into an engaging game. ## Git sync & workspace forks: your entire workspace, version controlled DevFeed: [Git sync & workspace forks: your entire workspace, version controlled]() Original publisher: [Read original article]() Author: Tristan Lécuyer Published: 2026-04-02T00:00:00Z Content type: release Language: en Sources: [Windmill Blog]() Topics: [Git](), [version-control](), [CI/CD](), [GitLab](), [GitHub]() Tags: [azure](), [bitbucket](), [ci-cd](), [fork](), [git](), [gitlab](), [launch-week](), [merge](), [pipelines](), [repository](), [review](), [rollback](), [sync]() ### AI overview Windmill introduces redesigned bidirectional Git sync and workspace forks. Git sync commits and pushes deployed items to a configured repository and can pull updates from Git, while forks provide isolated feature-development workspaces with deployment, merge, and Git-based workflows. ### Source excerpt Introducing improved Git sync and workspace forks: sync workspaces to Git, fork for feature development, and deploy via CI/CD. ## Security Week 2610: новые атаки на разработчиков ПО DevFeed: [Security Week 2610: новые атаки на разработчиков ПО]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-03-03T05:19:22Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Security](), [Next.js](), [bitbucket](), [Visual Studio Code]() Tags: [bitbucket](), [javascript](), [microsoft-defender](), [next-js](), [npm](), [security](), [tag-9fe8963de219](), [visual-studio-code]() ### AI overview A Microsoft report describes a cyberattack targeting software developers during job interviews. Victims receive a Next.js web application project hosted on Bitbucket, where malicious code can run through Visual Studio Code automation or when the project starts. The payload contacts command servers, searches for files and directories, and exfiltrates files. The article also briefly mentions other campaigns targeting Russian organizations. ### Source excerpt Совсем недавно мы писали о приписываемой северокорейской группировке атаке, целью которой были разработчики ПО, находящиеся в процессе поиска работы. На прошлой неделе исследователи компании Microsoft опубликовали отчет о еще одной похожей атаке. В более раннем исследовании основное внимание было уделено социальной инженерии, в то время как Microsoft подробно рассказывает о технической стороне атаки. Общая схема атаки показана на скриншоте выше. В процессе интервью разработчику присылают ссылку на код веб-приложения, написанного с использованием фреймворка Next.js. Код хранился на сервисе Bitbucket. Организаторы атаки предусмотрели несколько вариантов выполнения вредоносного кода, содержащегося в проекте. Например, может использоваться автоматизация для Visual Studio Code, которая дает команду на выполнение сразу после того, как разработчик открыл проект и обозначил его как доверенный. Читать далее ## First steps towards Codeberg DevFeed: [First steps towards Codeberg]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2025-12-31T11:43:33Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [Open Source](), [hosting](), [forgejo](), [Gitea](), [GitHub](), [bitbucket](), [passwords]() Tags: [article](), [bitbucket](), [coding](), [community](), [development](), [digitalsovereignty](), [engineering](), [forgejo](), [gdpr](), [git](), [github](), [hosting](), [inclusive](), [open-source](), [opensource](), [privacy](), [software]() ### AI overview An introductory tutorial about Codeberg, a community-driven, nonprofit platform for hosting software projects. The author explains its open-source, privacy-focused model and demonstrates registering an account and beginning to migrate a GitHub repository. ### Source excerpt A lot of Europeans are currently talking about Europe having to become more independent from US-based big tech. Being a European myself, I feel the need for this, too. However, just talking won't make a difference. So, why not make this our New Year's resolution? Here's mine: I love open source. Given GitHub's recent trajectory toward centralisation, I feel there are better-suited homes for my repositories. That's why I will start migrating them to Codeberg. What is Codeberg? Codeberg is a community-driven non-profit platform for hosting software projects. Many consider it the leading independent alternative to commercial services like GitHub and Bitbucket. While it looks and feels very similar to GitHub, its underlying philosophy and legal structure are fundamentally different: unlike GitHub, which is owned by Microsoft, Codeberg is run by a German non-profit organisation called Codeberg e.V.. It is funded by donations rather than venture capital or ads. The platform runs on Forgejo, which is a community-governed fork of Gitea. Therefore, the very software used to run the site is itself open source and transparent. And it is privacy-focused. Since Codeberg is hosted in the European Union (Germany), it adheres to strict GDPR standards. It does not track users for advertising and avoids black box AI features like GitHub Copilot. Does this sound appealing? To me it certainly did. That's why I decided to jump right in. In this introductory article, I'll show you my first baby steps, that is, registering and migrating the first GitHub repository. Signing up Registering is a very quick and pleasant experience. Visit https://codeberg.org, find and click the Register button. Just enter a username, your email address, a password, and the randomly generated number or word. Once you click on Register Account, you should receive an email with the inevitable confirmation link. Click on the link to verify your email address. You will be directed to your personal Codeberg landing ## Anatomy of a Pull Request Generator DevFeed: [Anatomy of a Pull Request Generator]() Original publisher: [Read original article]() Author: Shawn Sesna Published: 2025-10-02T14:48:57Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [argo-cd](), [pull-requests](), [Kubernetes](), [Git](), [bitbucket](), [Deployment]() Tags: [argo-cd](), [bitbucket](), [deployment](), [git](), [kubernetes](), [pull-request](), [technical-guides]() ### AI overview This tutorial explains Argo CD's Pull Request Generator, an ApplicationSet deployment type that monitors a Git repository for matching pull requests, deploys their manifests to ephemeral environments, and removes the deployed resources when the pull request closes. It also breaks down the manifest configuration, including polling intervals and Bitbucket Server settings. ### Source excerpt Argo CD has built a number of Generators to support various scenarios that developers need when using Argo CD and Kubernetes. In this post, I'll be discussing the Pull Request Generator. A Pull Request Generator is an Argo CD Application Set deployment type that is configured to "watch" a Git repository for Pull Requests (PRs). [...] The post Anatomy of a Pull Request Generator appeared first on Codefresh. ## One Go API over every SCM: go-scm in the internal developer platform DevFeed: [One Go API over every SCM: go-scm in the internal developer platform]() Original publisher: [Read original article]() Published: 2025-08-10T00:00:00Z Content type: article Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [internal developer platform](), [bitbucket](), [Go Language](), [GitHub](), [API]() Tags: [api](), [bitbucket](), [github](), [go](), [internal-developer-platform](), [pull-requests](), [scm]() ### AI overview The article explains how an internal developer platform can support Bitbucket Server, Bitbucket Cloud, and GitHub through the jenkins-x/go-scm Go API. It describes production fixes for provider-specific webhook, identity, pull request, pagination, permission, branch, build-status, and validation behavior. ### Source excerpt How the IDP supports Bitbucket Server, Bitbucket Cloud, and GitHub through jenkins-x/go-scm. ## CodeRabbit for AI-Assisted Code Reviews on GitHub, GitLab, and Bitbucket DevFeed: [CodeRabbit for AI-Assisted Code Reviews on GitHub, GitLab, and Bitbucket]() Original publisher: [Read original article]() Author: TheAnkurTyagi Published: 2025-07-25T07:23:06Z Content type: opinion Language: en Sources: [ByteSizedBets]() Topics: [ai code review](), [Code review](), [AI-assisted coding](), [GitHub](), [bitbucket](), [GitLab]() Tags: [ai](), [ai-code-review](), [ai-coding](), [automation](), [bitbucket](), [code-review](), [github](), [gitlab]() ### AI overview The article argues that AI code review tools can automate repetitive first-pass checks and reduce review delays while keeping human reviewers responsible for context, judgment, and final decisions. ### Source excerpt A hands-on look at how CodeRabbit automates the boring checks so you can ship faster without cutting corners. ## Introducing Nx Powerpack DevFeed: [Introducing Nx Powerpack]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2024-09-25T00:00:00Z Content type: release Language: en Sources: [Juri Strumpflohner]() Topics: [Open Source](), [GitHub](), [GitLab](), [bitbucket]() Tags: [bitbucket](), [enterprise](), [extension](), [features](), [github](), [gitlab](), [monorepo](), [nx](), [open-source](), [release]() ### AI overview Nx introduces Powerpack, a suite of paid extensions for enterprise needs. The article states that Nx remains MIT-licensed and open source, existing features remain free, and open-source maintainers can receive a free Powerpack license. ### Source excerpt Introducing Nx Powerpack, a paid extension suite for enterprise use cases, ensuring Nx remains open source and existing features are free. ## Deploy a Serverless FastAPI App with Neon Postgres and AWS App Runner at any scale DevFeed: [Deploy a Serverless FastAPI App with Neon Postgres and AWS App Runner at any scale]() Original publisher: [Read original article]() Author: Stephen Siegert Published: 2024-02-09T17:16:46Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [FastAPI](), [API](), [Serverless](), [Python](), [Database](), [Amazon Web Services](), [Framework](), [CI/CD](), [Deployment](), [Poetry](), [GitHub](), [bitbucket]() Tags: [api](), [aws](), [bitbucket](), [ci-cd](), [community](), [database](), [deployment](), [fastapi](), [git](), [github](), [poetry](), [python](), [serverless](), [web-applications]() ### AI overview A practical guide to building and deploying a scalable serverless API with FastAPI and Python. It uses AWS App Runner for managed application deployment, Neon Serverless Postgres for automatically scaling database compute, and AWS Systems Manager Parameter Store for secure connection management. The article also covers local development with Poetry and automatic deployment through repository commits. ### Source excerpt In this post, we'll guide you through setting up a scalable serverless API using FastAPI, deployed on AWS App Runner and powered by Neon Postgres as the serverless database. FastAPI is a modern, fast (high-performance), web framework for building APIs with Python 3.8+ based on st... ## Git hacks - a set of my favorite git aliases DevFeed: [Git hacks - a set of my favorite git aliases]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-27T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [Git](), [bitbucket](), [pull-requests]() Tags: [bash](), [bitbucket](), [commands](), [commit](), [git](), [git-aliases](), [linux](), [macos](), [pull-requests]() ### AI overview An overview of the author's favorite Git aliases for simplifying status and log checks, commits, branch management, reverts, and Bitbucket navigation. The article also describes aliases for extracting Jira ticket numbers and managing commit messages. ### Source excerpt I use Git a lot, even writing this article i will commit text few times. There's a set of aliases I rely on daily and they're first I add in new place. Some Git commands are unnecessarily verbose. You can make your life much easier with bash-completions, but if you write it tens of times per day, it's anyway a lot of typing... and I'm a lazy man 😄 Simple status/log checks git s s = status --short --branch --untracked-files Shows a short, branch-focused status with untracked files. ## Adding Snyk security to Jira and Bitbucket Cloud DevFeed: [Adding Snyk security to Jira and Bitbucket Cloud]() Original publisher: [Read original article]() Author: LaToya Muff Published: 2023-10-25T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Vulnerabilities]() Tags: [acquisition](), [atlassian](), [automation](), [awareness](), [bitbucket](), [blog](), [cloud](), [cloud-security](), [code-security](), [developer](), [devops](), [devsecops](), [how-to](), [integration](), [megawatt](), [related-content](), [scm](), [security](), [snyk-platform](), [supply-chain-security](), [vulnerabilities](), [workflow]() ### AI overview The article explains how integrating Snyk with Jira Cloud brings Snyk scan results and vulnerability triage into Jira. It describes creating and automating Jira issues for new vulnerabilities, along with assignments, severity thresholds, and SLA-based due dates. ### Source excerpt In this article, we'll discuss why and how to add Snyk security to Jira and Bitbucket. ## Forge: Deployment Webhook Improvements DevFeed: [Forge: Deployment Webhook Improvements]() Original publisher: [Read original article]() Author: Tim MacDonald Published: 2023-05-02T06:19:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Deployment](), [Laravel](), [bitbucket](), [GitHub](), [GitLab](), [ci](), [Code]() Tags: [bitbucket](), [ci](), [code](), [deployment](), [feature](), [git](), [github](), [gitlab](), [laravel](), [projects](), [source]() ### AI overview Laravel Forge has improved Quick Deploy for sites using custom source control providers. Forge can detect GitHub, GitLab, or Bitbucket repositories and use their native push webhooks to populate commit information in the Deployments table and expose it to deploy scripts. Sites using other providers or CI can now pass branch, commit hash, author, and commit message through reserved query parameters in the Deployment Trigger URL. ### Source excerpt Laravel Forge's "quick deploy" feature gives your team a seamless push-to-deploy experience. Whenever new code is pushed to your deployed branch, Forge will kick off a new deployment. This ensures tha... ## Run your Maestro Flows on Bitbucket Pipelines DevFeed: [Run your Maestro Flows on Bitbucket Pipelines]() Original publisher: [Read original article]() Author: Arthur Published: 2022-12-22T08:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [bitbucket](), [ci](), [API keys](), [configuration](), [App]() Tags: [api](), [app](), [bitbucket](), [build](), [ci](), [configuration](), [flow](), [integrations](), [pipelines]() ### AI overview This tutorial explains how to run Maestro Flows in Bitbucket Pipelines using the Maestro Cloud Bitbucket Pipe. It covers creating a Maestro Cloud account, securing an API key as a repository environment variable, storing Flow files, and adding the upload pipe to the pipeline. ### Source excerpt Maestro is compatible with all CI systems and provides native integrations with a number of common providers including Bitbucket Pipelines. ## How Badoo Increased Automated Merge Throughput DevFeed: [How Badoo Increased Automated Merge Throughput]() Original publisher: [Read original article]() Author: osmanov (Badoo) Published: 2021-06-21T10:00:02Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [Git](), [ci](), [bitbucket](), [GitHub]() Tags: [badoo](), [bitbucket](), [ci](), [continuous-integration](), [devops](), [git](), [github](), [jira](), [tag-5647dc7784f0](), [tag-e95ee8b94dca](), [teamcity](), [workflow]() ### AI overview A Badoo and Bumble release engineer explains how the team optimized automated Git branch merging for mobile projects. The article contrasts earlier sequential merging with a custom automerge system designed to increase throughput while maintaining process reliability. ### Source excerpt Меня зовут Руслан, я релиз-инженер в Badoo и Bumble. Недавно я столкнулся с необходимостью оптимизировать механизм автомерджа в мобильных проектах. Задача оказалась интересной, поэтому я решил поделиться её решением с вами. В статье я расскажу, как у нас раньше было реализовано автоматическое слияние веток Git и как потом мы увеличили пропускную способность автомерджа и сохранили надёжность процессов на прежнем высоком уровне. Читать далее ## Forge: Deploy Keys Now Supported DevFeed: [Forge: Deploy Keys Now Supported]() Original publisher: [Read original article]() Author: James Brooks Published: 2021-01-25T09:35:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Security](), [ssh](), [Laravel](), [PHP](), [bitbucket](), [GitHub](), [GitLab](), [Redis](), [MySQL]() Tags: [bitbucket](), [github](), [gitlab](), [laravel](), [mysql](), [php](), [security](), [ssh]() ### AI overview Forge now supports deploy keys, allowing servers to clone or pull only the specific repositories associated with newly created sites. Users can also provision servers without adding their SSH keys to connected source control provider accounts. ### Source excerpt Forge is used by agencies all over the world to provision servers and deploy sites on behalf of their clients. Currently, when Forge provisions a server, that server's SSH key is added to the SSH key... ## How to migrate GitLab/Bitbucket to GitHub in a simple way DevFeed: [How to migrate GitLab/Bitbucket to GitHub in a simple way]() Original publisher: [Read original article]() Author: Quang Nguyen Published: 2020-04-15T12:55:23Z Content type: tutorial Language: en Sources: [Android & Tech News -- Medium]() Topics: [GitHub](), [bitbucket](), [GitLab](), [Git](), [hosting]() Tags: [bitbucket](), [git](), [github](), [gitlab](), [hosting](), [how-to](), [ssh]() ### AI overview A tutorial explains how to migrate a repository from Bitbucket or GitLab to GitHub by creating an empty GitHub repository, changing the local remote URL, pushing the code and commit history, and optionally archiving the original repository as read-only. ### Source excerpt Checkout my latest app: Tinido. GitHub has just announced a happy news today for us, developers. "Teams on GitHub can create unlimited private repositories for free." So, here are their newest updates on the free package. Screenshot was taken on April 15th, 2020. Source (https://github.com/pricing) These changes are so competitive to other code hosting services like Bitbucket or GitLab. Many teams are going to relocate their projects to GitHub as I think. If you share the same idea and look for a simple way to migrate a repo from Bitbucket or GitLab, the followings are several simple steps to accomplish this. Inside your GitHub team page, create an empty private repo with the same name of Bitbucket/GitLab repo that you want to transfer. Copy your newly created repo link, either in HTTPS or SSH. For example, git@github.com:team-name/repo-name.git (SSH type) Inside your local project folder, change the remote URL under.git/config 's file to your copied GitHub's one. The content looks similar as follows. [remote "origin"] url = git@github.com:team-name/repo-name.git fetch = +refs/heads/*:refs/remotes/origin/* Do a git push: git push --all . It will push all codes and commit history on your newly GitHub repository. Done. After that, when we push new commits, it will push to GitHub only. The Bitbucket/GitLab repo now can be archived to 'Read-only' mode. Please get in touch with me via Github. Happy coding and have a good time! How to migrate GitLab/Bitbucket to GitHub in a simple way was originally published in AndroidPub on Medium, where people are continuing the conversation by highlighting and responding to this story. ## Automatic Merge of Pull Requests DevFeed: [Automatic Merge of Pull Requests]() Original publisher: [Read original article]() Published: 2020-03-01T07:01:57Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Azure DevOps](), [Pull Request](), [CI/CD](), [GitHub](), [GitLab](), [bitbucket]() Tags: [also](), [azure](), [bitbucket](), [continuous-integration](), [devops](), [github](), [gitlab](), [pull-requests]() ### AI overview This tutorial explains Azure DevOps Auto Complete for pull requests. It describes configuring branch policies and build validation so approved pull requests are merged automatically after the continuous integration build succeeds, with options such as squashing, rebasing, fast-forwarding, and deleting the merged branch. ### Source excerpt After using Azure DevOps for a while, I am totally sold on its Auto Complete feature for pull requests. While it does not apply universally, I do believe that any development process should be at the level where merging pull requests, or generalizing it, integrating all forms of contribution, should be as automatic and as hassle-free as possible. ## asciidoc documentation DevFeed: [asciidoc documentation]() Original publisher: [Read original article]() Published: 2019-10-24T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Documentation](), [Development](), [Code](), [Wiki]() Tags: [bitbucket](), [code](), [development](), [documentation](), [github](), [gitlab](), [html](), [markdown](), [pdf](), [repo]() ### AI overview This tutorial explores using Asciidoctor for technical documentation stored alongside source code. It explains how repository-based documentation can be kept current, updated by developers, and reviewed with code, while noting that larger documentation projects may benefit from features such as diagrams, source-code inclusion, and HTML or PDF export. ### Source excerpt One thing that a lot of people hate to do is writing documentation. Usually, it's postponed until development is finished and once it's done there is rarely time to do it properly. If you get past the struggle of writing it down there is always a problem of keeping it up to date. To avoid those pain points I'm going to explore what we can do with Asciidoctor to simplify this problem. Read more [Next page]()