ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #git
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Operating system: Linux git version: 2.26.2 Git repo provider of my repo: gitlab Repo provider of the failing submodules: Github .gitmodules [submodule "libraries/stb"] path = libraries/stb url = https://github.com/nothings/stb.git branch = master [submodule "libraries/harfbuzz"] path = libraries/harfbuzz url = https://github.com/harfbuzz/harfbuzz.git branch
I have a private repo with a GitHub Action that pushes the code to an AWS S3 bucket when there's a new push to the master branch. I need a pair of access keys to be able to push the contents and I'm storing them as GitHub Secrets and referencing them as environment variables in the build script. Now I would like to make this repo public in the near future, a
I created my first organization and invited a user to it. The user receives the email invitation and appears as a member of the organisation and project. However, when they click join in the email invitation they are denied access . The organisation is not connected to Azure Active Directory as suggested in Invited user Azure Devops project but they are unab
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
I know that you can revert back to a previous commit but it doesn't sound like the history will be gone. How can I revert back to a previous commit and make sure the commits that came after are gone forever?
I am creating a workflow in GitHub which creates and uses a docker image. Therefore I have started my workflow file with a global environment variable for this docker image which is visible for all the jobs in my workflow: name: continuous integration on: push: branches: - '**' env: IMAGE: docker.pkg.github.com/${{ github.repository }}/jactor-persistence:${{
Can't find any reference to the possibility to sign tags/verify signatures in Azure DevOps. Seems like you have to implement it yourself if you want to use it in Azure DevOps Pipelines. Am I missing something? Are there any plans in Azure DevOps to natively support this?
github
gitlab
docker