Skip to content

Instantly share code, notes, and snippets.

View gabydevdev's full-sized avatar

Gabriela Carral gabydevdev

18 followers · 73 following
View GitHub Profile
@gabydevdev
gabydevdev / commit-message-guidelines.md
Created June 13, 2025 15:18 — forked from JamesIves/commit-message-guidelines.md
🤖 Copilot commit messages instructions for VS Code

Add the following data to settings.json within VSCode to auto-generate commit messages with Copilot using the Conventional Commit format. This is based off of this example, however includes more explicit instructions for all commit prefixes (such as docs, refactor, etc).

  "github.copilot.chat.commitMessageGeneration.instructions": [
    {
      "text": "Generate commit messages in Conventional Commits format with gitmoji. Follow this exact structure:\n\n```\n<type>[optional scope]: <gitmoji> <description>\n\n[optional body]\n```\n\nExamples:\n- `feat(auth): :sparkles: add new login validation`\n- `fix(api): :bug: resolve user data fetch timeout`\n- `docs: :memo: update README installation steps`\n- `docs: :bookmark: add JSDoc comments to media component`\n- `style: :art: format code according to linting rules`\n- `refactor: :recycle: restructure video platform detection logic`\n\nTypes must be one of:\n- `feat`: A new feature\n-
@gabydevdev
gabydevdev / commit-message-guidelines.md
Created June 13, 2025 15:18
🤖 Copilot commit messages instructions for VS Code

Paste it to settings.json:

"github.copilot.chat.commitMessageGeneration.instructions": [
  {
    "text": "Follow the Conventional Commits format strictly for commit messages. Use the structure below:\n\n```\n<type>[optional scope]: <gitmoji> <description>\n\n[optional body]\n```\n\nGuidelines:\n\n1. **Type and Scope**: Choose an appropriate type (e.g., `feat`, `fix`) and optional scope to describe the affected module or feature.\n\n2. **Gitmoji**: Include a relevant `gitmoji` that best represents the nature of the change.\n\n3. **Description**: Write a concise, informative description in the header; use backticks if referencing code or specific terms.\n\n4. **Body**: For additional details, use a well-structured body section:\n   - Use bullet points (`*`) for clarity.\n   - Clearly describe the motivation, context, or technical details behind the change, if applicable.\n\nCommit messages should be clear, informative, and professional, aiding readability and project tracking."
  }
]
@gabydevdev
gabydevdev / .gitignore
Created April 3, 2024 18:38 — forked from salcode/.gitignore
Please see https://salferrarello.com/wordpress-gitignore/ for the canonical version of this WordPress .gitignore file. Note: I do not receive notifications for comments here (because GitHub does not send notifications on Gists)
# -----------------------------------------------------------------
# .gitignore for WordPress @salcode
# ver 20180808
#
# From the root of your project run
# curl -O https://gist.githubusercontent.com/salcode/b515f520d3f8207ecd04/raw/.gitignore
# to download this file
#
# By default all files are ignored. You'll need to whitelist
# any mu-plugins, plugins, or themes you want to include in the repo.
@gabydevdev
gabydevdev / sassas.md
Created May 27, 2022 20:31 — forked from AdamMarsden/sassas.md
Sass Architecture Structure

Sass Architecture Structure

sass/
|
|– base/
|   |– _reset.scss       # Reset/normalize
|   |– _typography.scss  # Typography rules
|   ...                  # Etc…
|
@gabydevdev
gabydevdev / acf-get-field.sublime-snippet
Created July 22, 2021 20:55 — forked from nashvillegeek/acf-get-field.sublime-snippet
Sublime Text 2 snippet for Advanced Custom Fields 'get field'
<snippet>
<content><![CDATA[
\$${1:varname} = get_field('${2:field_name}', '${3:\$post_id}');
if (\$${1:varname} != '') {
echo \$${1:varname};
}
]]></content>
<!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
<tabTrigger>acfgetfield</tabTrigger>
<!-- Optional: Set a scope to limit where the snippet will trigger -->
@gabydevdev
gabydevdev / BrowserDeviceInfo.js
Created June 8, 2021 20:43 — forked from TrevorJTClarke/BrowserDeviceInfo.js
A quick list of browsers and devices for use in testing. Chrome is used for all devices that need simulation.
var devices = [
{ name: 'Desktop - Huge', width: 2880, height: 1800, ratio: 2, type: 'desktop' },
{ name: 'Desktop - Extra Large', width: 1920, height: 1080, ratio: 1, type: 'desktop' },
{ name: 'Desktop - Large', width: 1440, height: 900, ratio: 1, type: 'desktop' },
{ name: 'Desktop - HiDPI', width: 1366, height: 768, ratio: 1, type: 'desktop' },
{ name: 'Desktop - MDPI', width: 1280, height: 800, ratio: 1, type: 'desktop' },
{ name: 'Laptop with HiDPI screen', width: 1440, height: 900, ratio: 2, type: 'desktop' },
{ name: 'Laptop with MDPI screen', width: 1280, height: 800, ratio: 1, type: 'desktop' },
{ name: 'Laptop with touch', width: 1280, height: 950, ratio: 1, type: 'desktop' },
{ name: 'Tablet - Portrait', width: 768, height: 1024, ratio: 1, type: 'tablet' },
@gabydevdev
gabydevdev / gist:e58ed97d8e4b8776150c57730facf77a
Created October 8, 2020 22:11 — forked from fat/gist:3744369
all you probably really need
/*! normalize-all-you-really-need-tho.css v1.0.0 | MIT License */
html {
font-family: sans-serif; /* 1 */
-webkit-text-size-adjust: 100%; /* 2 */
-ms-text-size-adjust: 100%; /* 2 */
}
body {
margin: 0;
@gabydevdev
gabydevdev / schema-org-structured-data-markup-using-microdata.html
Last active February 16, 2019 23:12 — forked from milanaryal/schema-org-structured-data-markup-using-microdata.html
An example of how to mark up a HTML5 webpage using the schema.org schemas and microdata.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<title>Site Title</title>
<link rel="stylesheet" href="/assets/css/style.min.css">
@gabydevdev
gabydevdev / sublime-text-remove-comments-css
Created July 7, 2018 02:56 — forked from schalkburger/sublime-text-remove-comments-css
Sublime Text regex to remove comments in CSS
(?s)/\*.*?\*/
@gabydevdev
gabydevdev / z-index.scss
Last active October 8, 2020 21:54 — forked from fat/gist:1f6da6b3bd0311a1f8a0
z-index scale
// Copyright 2014 A Medium Corporation
//
// z-index.less
// Medium.com's z-index scale. Z-index values should always be defined in z-index.less. This
// allows us to at a glance determine relative layers of our application and prevents bugs
// arrising from arbitrary z-index values. Do not edit the z-index scale! Only add application
// scoped z-index values.
// Z-Index Scale (private vars)