Gabriela Carral gabydevdev

Sass Architecture Structure

sass/
|
|– base/
|   |– _reset.scss       # Reset/normalize
|   |– _typography.scss  # Typography rules
|   ...                  # Etc…
|

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."
  }
]

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-

	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' },

	[
	"background",
	"background-attachment",
	"background-color",
	"background-clip",
	"background-image",
	"background-origin",
	"background-position",
	"background-position-x",
	"background-position-y",

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

	upload_max_filesize = 512M
	post_max_size = 512M
	memory_limit = 516M
	max_execution_time = 600
	max_input_vars = 5000
	max_input_time = 400

	/* ==========================================================================
	Include variables and mixins
	========================================================================== */
	/* ==========================================================================
	Typography variables
	========================================================================== */
	/* ==========================================================================
	Box variables
	========================================================================== */
	/* ==========================================================================

	# -----------------------------------------------------------------
	# .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.

	"github.copilot.chat.commitMessageGeneration.instructions": [
	{
	"text": "Follow the modified 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`) enclosed in square brackets [type] and optional scope in parentheses (scope).\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."
	}
	]