Jump to content

Search the Community

Showing results for tags 'github'.



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 21 results

  1. Search for emoji and copy them to the clipboard ?. Download v1.8.1 (2019-09-27) Usage: emoji [query] Press [return] (↵): Copy the symbol of the selected emoji (e.g. ?) to your clipboard. Press [alt]+[return] (⌥↵): Copy the code of the selected emoji (e.g. `:rofl:`) to your clipboard. Press [cmd]+[return] (⌘↵): Paste the code of the selected emoji (e.g. ?) to your frontmost application. Automatic Updates: This workflow will automatically check for updates at most once per day. If a new release is found, it automatically downloads and installs the latest version of the workflow. All downloads come directly from official GitHub releases. Optional Hotkey and Snippet Triggers: Customize the workflow with either a custom hotkey or a custom snippet. Links: GitHub Project Download New Releases GitHub Issues - (please submit bug reports and feature requests here) Screenshot:
  2. [I originally posted this on Reddit, but I'm posting again here to make sure that it's seen.] The tool itself is fine. Good improvements, but mostly invisible. My kids don't even know how to use the computer when they use a Mac without Alfred. Incredible software! I've been a user since 1.0 and a PowerPack user for just as long. Before that I used the Google task launcher thing, and before that, QuickSilver. What I'm interested in is a thriving workflow community. If you want to find workflows, you need to search too many places. Packal and Pacmax seem abandoned. You have the forums, Reddit, and random guesses in GitHub search. Consider the following to be feedback for improving the next generation of Alfred: Make it easier for users to get started: Enable them to click a link for a workflow, and have Alfred be the default handler instead of forcing me to download, find it, double-click it. Enable developers to define a setup flow, with some kind of standard UI. For example, I use a workflow for searching Atlassian Confluence wiki software (for work). Instead of having to type `confluence username` and `confluence password`, provide an up-front UI where a developer can ask these questions, and the user can answer them. This UI should be triggered the first time the user attempts to use the workflow (e.g., I type confluence, and the default option in an un-setup state is to start the setup). There should also be a way to validate these values before completing the setup (e.g., authentication to remote service was successful). One of the options in this UI would be to choose which keyword should be used to trigger it. The developer can provide a default, and the user can always go into preferences and change it, but being able to override the default keyword early would be a nice touch. For example, when installing the `pwgen` workflow, I always change the keyword to `pwd` because I can type it faster. Enable me to create different instances of the same workflow with slightly different configurations and map them to different keywords. For a concrete example, I want to have one instance of the Confluence workflow that searches ALL content (e.g., mapped to `conf {query}`), and another instance that can target a specific team's Confluence space (e.g., mapped to `team {query}`). Same workflow; slightly different configuration (in this case, search scope). If I search for something, but there are no results (or an error, or whatever), don't automatically fall-back to the catch-all options. If you recognize the keyword, have the top result say that there was a problem, and enable some way to view the logs and/or open the project in Finder. Perhaps this would be hidden behind an "I am a developer" checkbox in the preferences or something. Some kind of (better?) indicator in the UI when a workflow is waiting on the network. When I develop workflows, here's what would make it easier/better: Optimize some integrations with GitHub (first), then BitBucket or GitLab (after). Leverage things like topics (GitHub) and pull those in. Standardize on things like `alfred-v4` or `alfred-v3`, and `alfred-lang-php` or `alfred-lang-go`. Have a simple, built-in way to lookup and download any updates to workflows. First-party hooks, please. The solutions coming from the community don't last, and I'm tired of the churn. Make it easy to save credentials/secrets to the (encrypted) system keychain instead of making me write them (unencrypted) to disk. First-party hooks, please. Something like I say that this field is a secret and it should have a particular name. Alfred accepts the secret and stores it without me being able to see it. Integrate sanely with the macOS system logging, so that I can easily read errors in the Console.app. Make it easy for people to discover how to find the project and/or development code. Maybe something like `{keyword}?` (e.g., `conf?`) for easily discovering metadata about a workflow? Make it easy for people to report bugs/issues and send the developer some kind of debug/diagnostic data. Define strong standards/conventions that I can follow when creating workflows, so that you can read them and present them to users, without me having to duplicate my effort. One example is to leverage GitHub topics (mentioned above) and just pull them in to a centralized database of workflows. Why submit manually to another website when you can search the API and auto-populate data for a workflow to show to users? Right now, the results are always a single set of options (analogous to the HTML <select> field). I would love to be able to set up the equivalent of an HTML <optgroup> in the results — a way to group them. For example, "here are the exact matches, then here are the fuzzy matches). HTML <optgroup> is an exact grouping (i.e., one group, then the next group). The group could have a label defined which provides instructions. Something like "Choose a language…". (Provide a link in the docs which point to Apple's HIG so that people know how the ellipsis character should be used in menus and buttons.) Having a way to add an icon to the left/right-edge that is vertically/horizontally centered and not inline with the other text would be a good way to flag certain results as standing out. For example, here are the search results from hub.docker.com. These are from the community, but these (with a star/checkbox/smiley-face on the left-edge) are official. I haven't looked at the multi-level query stuff yet, and you may have already done this, but supporting/auto-completing enums after the keyword would be awesome. Also wrapping enums in the previous suggestion as a group with a label, to allow developers to provide more context, would be awesome. Different versions of macOS include different versions of language runtimes (and Apple's documentation says that language runtimes will stop shipping by default in upcoming versions of macOS). There should be a way for the developer to specify binaries (detected by /usr/bin/env is preferable over hard-coding a path, like many hash-bangs) and versions that are required to run. This should be validated at install time, not at run-and-fail-time. If the current system does not meet the requirements, then the developer should be able to provide instructions and/or a setup script that can be run by Alfred (with user confirmation + sudo password, if necessary) to install any prerequisites. So, an install-time script to detect, and a setup script which can install missing dependencies. All would happen during this hypothetical "Setup" wizard. Some kind of package signing. Public/private key? GPG? User-facing warnings about installing unsigned workflows. Don't need to go full-scale notarization (yet), but let's see what the ecosystem does as a result. Streaming results. We define the format of the individual results, and as data comes back (e.g., fetching API results across pagination), we can append/prepend/overwrite results. `fzf` is an example of a CLI tool that can update results as new data streams in. Being able to filter those streaming results in real-time with fuzzy-matching would be mind-blowing. Some kind of background/async support. Example of background support: I install a workflow which lets me keep an eye on stock prices. This workflow has the ability to watch a particular stock, and can send a notification when it crosses a threshold or moves so many percentage points up/down. To me, background == polling/scheduled/cron-ish, but maybe I'm not thinking big enough. Example of async support: I want to use Alfred's file selection support to find a directory containing FLAC audio files, then pass that directory (or files) to a workflow which calls out to FFMPEG and converts them all to MP3 @ 96kbps (muah-hah-hah!). When the task is complete, I would get a notification. When clicked, Alfred would open with a new selection of MP3 files that I can take the next action on (open in iTunes/Apple Music/QuickTime Player). A single, canonical place to find reasonably-curated workflows. Preferably owned and maintained first-party. Yes, it means running some servers and doing some work to curate. Not sure how practical that is for a small team, but it's necessary. When I look for workflows, here is what I want to know: What are the user ratings? (this means finding an easy way to enable users to rate the workflows they use and collect that anonymized data) What language(s) is this written in? (Can I contribute or hack at it if I want? What language do I need to know? Do I have that runtime installed?) What version of Alfred is this optimized for? (The first results on Packal are ≥ 5 years old) How many workflows of the exact same thing already exist? (Should I re-think writing my own and just use or contribute to an existing one?) Is this maintained? Is this maintained by a trusted developer? Or just some dude on the Internet somewhere? What new (or newly-updated) workflows are available which support (a) the latest version of Alfred, (b) whatever cool new feature of Alfred, (c) some other notable thing? Apple's App Store does this and it's a great way to find the signal amidst the noise.
  3. I am trying to write an workflow that will do following things in github page: - go to the bottom of the page - click commit button The main thing is whenever we are editing a file in github online to commit the chages we have to go to the bottom of the page and click "Commit changes" button. The github does not have that button on the top of the webpage and also does not have keyboard shortcut to do that. Commiting and Pushing edited files from a terminal is pretty simple a simple bash function in `bash_profile` will do that easily, but while working on online pages, we need to scroll down each time if we need to commit the changes. It will not save a heavy amount of time but if it is possible, the Alfred workflow to do it worth it. Thanks.
  4. I'm trying to install this chrome history workflow (https://github.com/tupton/alfred-chrome-history), but I'm not versed in terminal or coding at all. Can anyone further dumb-down the FROM SOURCE section of this repo for me to understand? Much appreciated.
  5. For those who uses github and markdown, I have created a simple workflow to automatically create the Table Of Contents for the markdown files. The github website is: https://github.com/bhishanpdl/Alfred_MARKDOWN_TOC We can also find this package in packal.
  6. Awesome Lists This workflow lets you search for any awesome list on GitHub. The awesome lists searched can be found here. For more information, on how you can use the workflow, you can read the GitHub readme. In the future I want to make it so that you can go inside each of the awesome lists and view the links of all awesome lists inside Alfred. But this is a bit challenging I found so I am going to try it on Learn Anything Curated Lists first as they follow a very similar structure and I can use that to my advantage. Hope you like it. Code | Download
  7. 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.
  8. There is this awesome workflow that exists on the Internet. That is a shame that it is not posted either here or on Packal. It does this awesome thing where it downloads all your starred repositories to an SQLLite database and lets you query these repos. It is super fast. I modified it a little though to make it so that pressing different modifier keys open different pages related to the repo. So for example simply pressing return will open the repository, fn + return will open issues of that repo, cmd + return will open an issue related to the repo and cntrl + return will clone that repo to a folder you specify. Mine is specified as ~/play but you can change it. Here is the original workflow, credit to the author. And here is the download of my modification of the workflow with changes I mentioned above. It does help to have over 3000 starred repositories but it is still super useful I think and will save many hours from your life. As bonus I schedule to run the update script once a day with Keyboard Maestro : You can probably do it with Launchd but Keyboard Maestro is more familiar to me.
  9. I am builing my first workflow that i wan tto make public available. Therefor I need it to have an auto update function, because i want to be able to have extre features implemented in the future. But, I am new to prgramming and github. But found an interesting article about this http://alfredworkflow.readthedocs.io/en/latest/user-manual/update.html But I have no idea where to do this configuration shizzle: Anyone here that knows how to do this and can help me out?
  10. Hello, I created a small workflow to quickly search through your starred repositories on GitHub. After the keyword "ghs" it matches the argument against title and description of the repository. At the first start you have to set your GitHub username with "ghsset user". Also the first run will be slow (depending on how many Stars you have), since it fetches all the user avatars (if anyone has an idea to make this more smooth let me know!). You can download it here (GitHub). I was inspired to create this after seeing Adam Simpsons workflow for StackOverflow Favorites. Hope it is useful for someone!
  11. It works similar to the GitHub command bar and to its update, the keyword is "gh" (example: "gh github/gollum issues"). With enter you can open the entry in your default browser. If you just want to copy the URL of a repo/user/issue, hit cmd+c on an entry. Hit cmd+enter to paste the URL to the front most app. With shift or cmd+y you can open the URL in QuickLook. You have to login (gh > login <user>) before you can use the workflow. The login command opens a dialog box for the password. The workflow does not save the plain password, only a cookie for the login. DOWNLOAD | GitHub Repository | Command list
  12. Here's the link: https://github.com/Derimagia/awesome-alfred-workflows I didn't see an awesome list for Alfred so I made one! Would really appreciate it if anyone wants to contribute anything. If you don't know how to do a pull request and you think there's a workflow that's truly "awesome", post an issue! A lot of people seem to be liking it but I want this to be a community thing and right now it's mostly workflows I use.
  13. Can I get some tips on how would I create a workflow that will https://github.com/my_org/my_repo/compare/start_sha...end_sha I'd like my_org to be fixed or from a list to autocomplete. The same for my_repo. And then I'd like to capture shart_sha and end_sha. And then open up chrome with this URL. Any tips on how to do this?
  14. Hello - I've developed a workflow for using github gists service as a snippet manager. You simply provide your username and a personal access token and the workflow downloads all of your gists (saving them locally) and enables them to be searched. I've implemented functionality beyond what the github gist service offers including browsing gists by tags (specified with a # sign) and browsings gists by language. Download here Github page Note that downloading gists takes a minute or so if you have a lot. They need to be manually reloaded currently. Let me know what you think! Thanks. Screenshots
  15. 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
  16. juanra

    Flat Alfred

    Hi all of you, I was looking for a theme that was aligned with the flat design philosophy but didn't find one that made me smile. I decided to make one from scratch, using Flat UI colors and OSX BlueGreen theme as a base. I want to do dark and light versions with every accent color but i need your help, so fork it on Github and help me. Here is my approach, I hope you enjoy it:
  17. I've tried a few github workflows. Most don't have user auth built in, or if they did, sent the password in the request (which is not secure!). So I build a new one with a few more features and followed Githubs best practices for auth security. Hope everyone likes it. If you'd like other APIs support just let me know. https://github.com/willfarrell/alfred-github-workflow
  18. 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
  19. 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?
  20. 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!
  21. Just wanted to make my contribution to the v2 themes out there so made these clean ones. I hope to make some more when I get the time/inspiration. (I'm rocking Omar, personally.) https://github.com/Nephets/simple-alfred-themes
×
×
  • Create New...