DEV Community: Deshan Madurajith

Get Scraped Shopify App Store Data For Free

Deshan Madurajith — Thu, 25 Jul 2024 16:59:32 +0000

I wanted to see what Shopify apps are out there and find out what's missing or could be better. So, I scraped the Shopify app store and got a bunch of data like app titles, developers, ratings, reviews, and descriptions.

I don't want to waste your time with a long blog. Just download the dataset here for Free - Download Dataset

What I Found

Many Shopify apps focus on product reviews, store locators, SEO tools, and return management. Some apps have high ratings but few reviews, indicating a need for more promotion. Others with lots of reviews but lower ratings could improve their features or support. Pricing varies widely, with free and paid plans available.

Opportunities

Better Integrations: Apps that work well with other tools (like email and CRM) could be really useful.
More Insights: Apps that offer deeper analytics and actionable data could stand out.
Improved User Experience: Easy-to-use apps with good support can make a big difference.

Conclusion

There's a lot of room for new and better apps in the Shopify store. If you're a developer, check out the data, and you might find your next big idea!

Download the dataset for free and start exploring. Let me know if you create something awesome!

Happy building! 🚀

Download Dataset

Pick a commit from another branch to the current branch (cherry-pick)

Deshan Madurajith — Sun, 26 Jul 2020 18:30:43 +0000

When to use cherry-pick

Always try to not to use cherry-pick because it can make a duplicate commit.
If you have already committed something on another branch, you can pick it and merge it with your working branch. Example: you may need a hotfix commit from another branch.
Restoring lost comments. Sometimes a pull request might get closed without merging. But you can see those commit in the git log. So you can cherry-pick them

Steps

1. Get the hash of the required commit

Checkout to the branch that has the required commit. Then get git hash of that commit by using CLI or Github site



git log --oneline 
git reflog

or you can view your git as a graph



git log --graph --oneline --all

2. Cherry-pick the commit

Checkout to the brach that you want to add the commit. Enter the following command.
git cherry-pick commit-id. example:



git cherry-pick c67a4b7

if you want to add only the content without commit. You can add --no-commit



git cherry-pick c67a4b7 --no-commit

Change Git user for a specific repo

Deshan Madurajith — Wed, 22 Jul 2020 19:01:14 +0000

Sometimes you may work on multiple projects using multiple git users. Your personal project with your personal GitHub and office GitHub with your business email. You may need to commit like someone else 🤫. There are two options to change git author of your repository.

1. Change without Terminal

Go to your repo folder & show hidden folders
Go to .git hidden folder and open config file
Add/replace the following block in the config file

[user]
    name = deshan
    email = deshan [at] dev.to

Now you can commit a new change and check author information.

2. Change with Terminal

Open the terminal and go to the repository. Enter the following command

git config user.email "deshan@dev.to"
git config user.name "deshan"

If you want to change the author for previous commits, follow this replace-accidentally-committed-git-author-information-from-git-history

Replace accidentally committed git author information from git history

Deshan Madurajith — Tue, 21 Jul 2020 19:37:53 +0000

If you working for multiple projects or companies, you may use different Github logins. If you accidentally commit something as wrong git user, it will be a pain to change the history. If you push it and add more commits on that it will be more painful to revert those changes.

If you search on google, you will see a lot of solutions. Most solutions are not straight forward, you have to spend few minutes to hours to realize the solution because of many CLI commands and copy pastings. But did you know that you can replace author name and email in the entire git history with a script?

You don’t need to use git CLI commands to change the author's name and email in the commit history. You can just run a script to replace all the commits assigned to the wrong git author.

The following illustration shows the high-level solution. Using a script, you can replace the author. This script will

not change committed dates
not change committed messages

Warning* 👿 - This will change the git hashes of the commits.

Step (1/4): Create a fresh, bare clone of your repository

Bar clone means it does not have a git working directory. It has only .git data.

git clone --bare https://github.com/user/repo.git
cd repo.git

Step (2/4): Create script.sh file, update and execute

Open this script and change following OLD_EMAIL, CORRECT_NAME & CORRECT_EMAIL

#!/bin/sh

git filter-branch --env-filter '

OLD_EMAIL="your-old-email@example.com"
CORRECT_NAME="Your Correct Name"
CORRECT_EMAIL="your-correct-email@example.com"

if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
then
export GIT_COMMITTER_NAME="$CORRECT_NAME"
export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
fi
if [ "$GIT_AUTHOR_EMAIL" = "$OLD_EMAIL" ]
then
export GIT_AUTHOR_NAME="$CORRECT_NAME"
export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
fi
' --tag-name-filter cat -- --branches --tags

Give executable permissions: You need permission to execute the shell script. You need to give executable permission
sudo chmod 755 script.sh

Let's run:Time to run the shell script. This script will not push those changes to your origin. So, you can review after executing.
./script.sh

Step (3/4): Review your git log

Check author name, email, and commits messages.

git log
git log --decoreate --oneline      # one line log

Step (4/4): Push to Github

Check twice before you run the following command.
git push --force --tags origin 'refs/heads/*'

👿Warning👿 - Once you run this script, your commit hashes will be changed

because of hash changes - When you get a git pull, you will see something like this

Your git users will have to run following command to avoid that issue

git pull --allow-unrelated-histories

References

https://docs.github.com/en/github/using-git/changing-author-info

Also, read How to change git user for specific repo