- Create repo on GitHub where you'll put your files.
- Use jsDeliver or statically to get your assets.
Here is repo I'm using:
https://github.com/jcubic/static
And links to files look like this:
| local cmp = require("cmp") | |
| local capabalities = vim.lsp.protocol.make_client_capabilities() | |
| capabalities = require("cmp_nvim_lsp").default_capabilities(capabalities) | |
| local mason = require("mason") | |
| local mason_lspconfig = require("mason-lspconfig") | |
| cmp.setup({ | |
| snippet = { |
| --- Utility functions to aid development of other modules | |
| --- | |
| --- @module utils | |
| local M = {} | |
| function M.get_file_extension(path) | |
| return path:match("^.+(%..+)$") | |
| end | |
| function M.get_file_name(path) |
| --- Defines the bindings for various operations performed by the LSP with combination of | |
| --- chords. | |
| local map = require('utils').remap | |
| local M = {} | |
| M.on_attach = function(client, bufnr) | |
| client = client | |
| buffer = bufnr |
| -- This configuration file is licensed under the MIT License | |
| -- The user (You) is permitted to modfiy, use or re-distribute the configuration | |
| -- file as he/she/they/them/other see pleased. | |
| -- | |
| -- It would be nice, if you could mention the author. Thanks! | |
| -- Global configuration | |
| -- | |
| -- :h <options> would give you the options |
Here is repo I'm using:
https://github.com/jcubic/static
And links to files look like this:
| ############## | |
| # Docker Compose File | |
| # Maintainer: Eri Adeodu (@50-Course) | |
| # License: MIT License. | |
| # | |
| # Reference links: | |
| # incase you feeling adventerous, | |
| # - https://docs.docker.com/compose/compose-file/ | |
| # - https://nickjanetakis.com/blog/best-practices-around-production-ready-web-apps-with-docker-compose | |
| # - https://https://hackmamba.io/blog/2022/09/best-practices-when-using-docker-compose/ |
The Shields service (at shields.io) provides a way to create custom badges for your projects. These are badges are very common and are frequently used to show status information about the project, or demonstrate tools that were used for the development of your project.
People
:bowtie: |
π :smile: |
π :laughing: |
|---|---|---|
π :blush: |
π :smiley: |
:relaxed: |
π :smirk: |
π :heart_eyes: |
π :kissing_heart: |
π :kissing_closed_eyes: |
π³ :flushed: |
π :relieved: |
π :satisfied: |
π :grin: |
π :wink: |
π :stuck_out_tongue_winking_eye: |
π :stuck_out_tongue_closed_eyes: |
π :grinning: |
π :kissing: |
π :kissing_smiling_eyes: |
π :stuck_out_tongue: |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
| Commit type | Emoji |
|---|---|
| Initial commit | π :tada: |
| Version tag | π :bookmark: |
| New feature | β¨ :sparkles: |
| Bugfix | π :bug: |
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages