Jump to content

Search the Community

Showing results for tags 'git'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 11 results

  1. # Gitmoji Workflow for Alfred Link > [Gitmoji](https://github.com/carloscuesta/gitmoji) is an initiative to standardize and explain the use of emojis on GitHub commit messages. Search gitmojis and then copy to clipboard, So you don't have to remember what the emoji means. ## Install 1. [Download](https://github.com/Quilljou/alfred-gitmoji-workflow/releases) 2. double click to install([Alfred](https://www.alfredapp.com/) is required) ## Usage Type `gitmoji` in Alfred will list all gitmojis. Also you can search gitmojis with description or name given in [gitmoji](https://gitmoji.carloscuesta.me/). Then `enter` to copy to clipboard. Also It' will automatically paste to front most app. ## Others - Data is from [gitmoji](https://github.com/carloscuesta/gitmoji), This workflow will update data once a week. - Inspired By [alfred-github-workflow](https://github.com/gharlan/alfred-github-workflow) and [alfred-caniuse-workflow](https://github.com/willfarrell/alfred-caniuse-workflow) - Thanks for [Workflows](https://github.com/jdfwarrior/Workflows) - Related to [alfred-emoji-workflow](https://github.com/carlosgaldino/alfred-emoji-workflow) ## :bug: Bug Type `gitmoji` first will show nothing, It will be fixed in second typing.
  2. Alfred Git Repos Workflow Browse, search and open Git repositories from within Alfred. Download Get the workflow from GitHub or Packal. Usage This workflow requires some configuration before use. See Configuration for details. repos [<query>] — Show a list of your Git repos filtered by <query> ↩ — Open selected repo in app_1 (see configuration) ⌘+↩ — Open selected repo in app_2 (see configuration) ⌥+↩ — Open selected repo in app_3 (requires configuration) ^+↩ — Open selected repo in app_4 (requires configuration) ⇧+↩ — Open selected repo in app_5 (requires configuration) fn+↩ — Open selected repo in app_6 (requires configuration) reposettings — Open settings.json in default JSON editor reposupdate — Force workflow to update its cached list of repositories. (By default, the list will only be updated every 3 hours.) reposhelp — Open this file in your browser Configuration Before you can use this workflow, you have to configure one or more folders in which the workflow should search for Git repos. The workflow uses find to search for .git directories, so you shouldn't add huge directory trees to it, and use the depth option to restrict the search depth. Typically, a depth of 2 will be what you want (i.e. search within subdirectories of specified directory, but no lower). Add directories to search to the search_dir array in settings.json (see below). The default settings.json file looks like this: { "app_1": "Finder", // ↩ to open in this/these app(s) "app_2": "Terminal", // ⌘+↩ to open in this/these app(s) "app_3": null, // ⌥+↩ to open in this/these app(s) "app_4": null, // ^+↩ to open in this/these app(s) "app_5": null, // ⇧+↩ to open in this/these app(s) "app_6": null, // fn+↩ to open in this/these app(s) "global_exclude_patterns": [], // Exclude from all searches "search_dirs": [ { "path": "~/delete/this/example", // Path to search. ~/ is expanded "depth": 2, // Search subdirs of `path` "name_for_parent": 1, // Name Alfred entry after parent of `.git`. 2 = grandparent of `.git` etc. "excludes": [ // Excludes specific to this path "tmp", // Directories named `tmp` "bad/smell/*" // Subdirs of `bad/smell` directory ] } ] } This is my settings.json: { "app_1": "Finder", "app_2": ["Finder", "Sublime Text", "SourceTree", "iTerm"], "app_3": "Sublime Text", "app_4": "SourceTree", "app_5": "iTerm", "app_6": "GitHub", "global_exclude_patterns": [], "search_dirs": [ { "path": "~/Code" }, { "path": "~/Sites" } ] } Search Directories Each entry in the search_dirs list must be a mapping. Only path is required. depth will default to 2 if not specified. excludes are globbing patterns, like in .gitignore. name_for_parent defaults to 1, which means the entry in Alfred's results should be named after the directory containing the .git directory. If you want Alfred to show the name of the grandparent, set name_for_parent to 2 etc. This is useful if your projects are structured, for example, like this and src is the actual repo: Code Project_1 src other_stuff Project_2 src other_stuff … … Open in Applications The applications specified by the app_N options are all called using open -a AppName path/to/directory. You can configure any application that can open a directory in this manner. Some recommendations are Sublime Text, SourceTree, GitHub or iTerm. Note: As you can see from my settings.json, you can also set an app_N value to a list of applications to open the selected repo in more than one app at once: … "app_2": ["Finder", "Sublime Text", "SourceTree", "iTerm"], … You can also use → on a result to access Alfred's default File Actions menu. License, Thanks This workflow is released under the MIT Licence. It uses the Alfred-Workflow and docopt libraries (both MIT Licence). The icon is by Jason Long, from git-scm.com, released under the Creative Commons Attribution 3.0 Unported Licence.
  3. Alfred Commit Folders Simple workflow that lets you search folders and then write a commit message. It would then git add and git commit all files in the folder with the message you provide. And finally it would git push the changes. This workflow assumes that the folder you select is already initialised with git as it is a file filter that searches through all the folders. It will however warn you if the folder you chose is not under git. You can of course modify the scope of the search or even make it that it only searches through git initialised folders but for my use case, I use this workflow when I make a change to some README file in some folder and want to quickly commit it without going to my terminal. For quickly editing README's of folders I use this workflow that searches through all folders and with a modifier key press will open the README in the markdown editor you set up. There is also alternative action that will commit only the README file inside the folder with a predefined commit message. Again all the commit messages can be customised to what you prefer. Download You can install the workflow from GitHub releases and you can find more information on it on GitHub. Hope you like it. ?
  4. A snippet pack to make putting the true unicode equivalents of things like :sparkles:, :lipstick:, and other emojis used in git commits easier to type. It gives them names relevant to coding. Of course the official gitmoji has a CLI but suppose you want to use an IDE or don't want to install npm but already have Alfred Powerpack, or you just want a more inline way way of adding emoji, or you want the emoji to work with $git log (e.g. :sparkles: will not be interpreted by git log); if so, this is for you. Examples: :sparkles: -> :add: Because one uses ✨ when adding new features :penguin: -> :lin: Because one uses ? when making linux related changes :checkered_flag: -> :win: Because one uses ? for windows related changes :heavy_plus_sign: -> :+dep: Because one uses ➕ when adding dependencies etc.. Added benefit of making emojis appear with $git log because they are just unicode after using this. Inspired by: https://gitmoji.carloscuesta.me/ And also: https://github.com/atom/atom/blob/7929e261a0d6e78ff4ca5196c8b385946e64dbd9/CONTRIBUTING.md#git-commit-messages Full mapping details and download is available on the github
  5. Description This workflow allows you to create .gitignore files with Alfred. It uses the templates from the github/gitignore repository, and combines them into a single file that you can copy into your project. The templates are stored on your machine, so you have easy access to them, even when you are on the move and don't have internet connectivity. Download The workflow can be downloaded from Packal: gitignore by jdno Requirements Although it should be pretty self-explanatory, these are the requirements for this workflow: OS X Alfred 2 Git Installation After installing the workflow, you need to download the templates. Enter the following command into Alfred: gitignore-update Executing this will clone the github/gitignore repository, and make the templates in it available for offline use. Usage To use this workflow, simply type in: gitignore You will now see a list of all templates installed on your machine. You can search for specific templates by typing in their name. Selecting a template will place add it to the command line. If you've selected all templates that you want to combine, simply select the first item in the list called "Build .gitignore file". This will start the generation of the template, and open it in TextEdit once it has been created. Copy & paste the contents of the file and paste them into the `.gitignore` file in your project. Have fun! I hope some of you will find this workflow useful. If you experience any problems, please tell me so that I can fix them.
  6. Quickly access your Tower git repositories I finally got around to checking out Alfred today, and I was so blown away by the workflows feature that I decided to write one. Github: https://github.com/cjlucas/tower-alfred-workflow The latest packaged workflow can be found here. I will be checking for bug reports here as well as on Github. It'll be easier to diagnose bugs if I have your Tower bookmark's file as well (it can be found here: ~/Library/Application Support/Tower/Bookmarks.plist). If you'd prefer to not have it posted in public, you can send me a message on here or on Github.
  7. edgarjs

    Github repositories

    Hey guys, just finished my first workflow for Alfred. I'm always finding my self going to github.com and then looking for the repository I want to see, this has been exhausting and it's too many steps to do many times a day. So I thought a nice workflow would make things easier. It's as simply as typing "gh REPONAME" to get results and open the repo URL quickly. Hope you find it useful. http://www.packal.org/workflow/github-repos
  8. Shorten GitHub URLs with Git.io. Simply use the keyword gitio with the GitHub URL as the argument. The shortened URL is automatically copied to the clipboard. Important: Git.io is NOT a general purpose URL shortener. It will only shorten github.com URLs. This is mostly useful to software developers Download from here: randomerrata.com/post/50157813021/git-io
  9. I've been developing my first few workflows, and I'm following a development model that looks like: - Have a git repo somewhere on my local machine that's pushed to github. - Symlink that directory into the Alfred workflow preferences folder - Alfred workflow preferences is under Dropbox, so it syncs between machines. A few questions have come up as I get deeper into this. 1. When I do an export of a workflow in Alfred preferences, so I can share the latest version with the world, does that package up the entire directory? Meaning, all the .git directories, project history, etc? 2. Is this symlink model the preferred way to handle things? Or do experienced devs find it's better to write a script to "install" a workflow standalone, because it causes less conflicts and problems. (one example is that Alleyoop won't find equipped workflows if they are symlinked, but I suspect other issues might arise with workflows or Alfred itself) (update: Alleyoop 2.552 and above now respects symlinked directories) Any other tips from experienced developers on git-managed workflows?
  10. RevellNL

    Github workflow

    Github workflow for Alfred v2 A configurable workflow for Alfred v2. Installation You can install this workflow by dowloading the Github.alfredworkflow file and either double-clicking it, or dragging it onto the Alfred Workflow screen. After adding it to your workflow collection, when you run the gh command in Alfred you will be presented with only two options; auth and token. First, you'll need to choose for the auth option, this will generate an OAuth token for you which will be used by all subsequent calls to the Github API. Once you get the OAuth token, copy it from the website, run gh token and paste the OAuth token in the Alfred window. gh token thisisthetokenwhichcamefromthewebsite Now you're all set to start using this workflow! Usage The initial command for starting this workflow is gh. The commands currently supported by this workflow are: repo This returns a list of options for listing your repositories You can filter the results show by typing (part of) the repositoryname after the workflow command, f.e.: If there's anything you run into which isn't working as you expect, or not working at all for some reason. Please, do let me know! Also, be sure to check out the repository and maybe make some additions yourself!
  11. leenug

    Beanstalk Repos

    Alfred-Beanstalk A quick and dirty Alfred workflow that allows you to list and search through your Beanstalk repos. Setup Couldn't be simpler, just put your account, username and password into the $credentials array. Usage The repo clone string is copied to your clipboard, looks like: git clone git@account.beanstalkapp.com:/repo.git -o Beanstalk bs list - lists all repos bs Search {query} - searches for repos containing {query} Download https://github.com/Leenug/Alfred-Beanstalk Hope this is useful, and would love to hear your feedback and ideas on how to improve this!
×