developer resources
Codebales holds an ever growing number of solutions to problems that we have experienced in our day to day code writing
Selected filter
35
results
Andrew Fletcher
•
In our projects, team members frequently generate new Git branches linked to the same Jira number, resulting in cluttered and disorganised structures that can pose challenges for both current and future developers. For instance:
Jira: ABC-123
Ticket work: Reformat headers
Over time, these branches accumulate and become disorganised, resulting in names like:
ABC-123-reformat-headers
ABC-123-format-headers
ABC-123-format-header
This can lead to a cluttered and inefficient workflow. It's preferable...
Andrew Fletcher
•
I'm receiving an issue with a previous release on Google...
Andrew Fletcher
•
The "keystore password was incorrect" error in keytool indicates that the...
Andrew Fletcher
•
How to generate a new private key and submit it to Google Play for signing your...
Andrew Fletcher
•
git reset, git revert, and git cherry-pick are three Git commands used for...
Andrew Fletcher
•
git clone git@bitbucket.org:{username}/{repo}.git
And I was unceremoniously delivered the following error
fatal: could not create work tree dir '{project}': Permission deniedMy initial thought was the error due to server permission... being sudo. This was tested by running the command
sudo git clone git@bitbucket.{username}/{repo}.git
Which generated the error
Cloning into 'repo'...
git@bitbucket.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make...
Andrew Fletcher
•
Resources - changing Drush
Type
Version
Drush (current)
11.6.0
Drush...
Andrew Fletcher
•
Something I haven't had to do in a while is to change the name of a Git branch...
Andrew Fletcher
•
Git filename error when running the git add command. The error I'm...
Andrew Fletcher
•
Attempting to run a composer update command, you know the one used...
Andrew Fletcher
•
Post creating a new branch in the repo, next step was to run the checkout command locally. On my local environment I ran the following command
git checkout {branch-name}However, the response was
error: pathspec '{branch-name}' did not match any file(s) known to git
Solution
The issue while the new branch is known in the repo, it's not known in my local environment. To make the new branch known you need to run the fetch command
git fetch --allResponse
remote: Enumerating...
Andrew Fletcher
•
Issues with sign in key...
When attempting to upload a APK package, I'm getting...
Andrew Fletcher
•
Using Composer to Manage Projects and if required their dependencies
In this...
Andrew Fletcher
•
I'm in an environment where the default branch is staging and I'm attempting to...
Andrew Fletcher
•
Looking at composer I first wanted to check the current version, which is...