Initialize the Astro project #1
Conversation
5ouma
commented
Nov 7, 2024
5ouma
commented
- Apply the Astro empty template
- Add repository related files
The empty template was applied.
WalkthroughThis pull request introduces several new configuration files and templates to enhance project management and community engagement. Key additions include a Contributor Covenant Code of Conduct, a contributing guide, and structured issue templates for feature requests and bug reports. GitHub Actions workflows for CI, release automation, and Bun setup are also included. Furthermore, configuration files for pre-commit hooks and Renovate are established to improve code quality and dependency management. Overall, these changes aim to create a more organized and inclusive development environment. Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (24)
✅ Files skipped from review due to trivial changes (14)
🧰 Additional context used🪛 LanguageTool.github/CODE_OF_CONDUCT.md[style] ~32-~32: Try using a synonym here to strengthen your wording. (COMMENT_REMARK) .github/SECURITY.md[style] ~5-~5: Consider using a different verb to strengthen your wording. (FIND_ENCOUNTER) 🔇 Additional comments (11).github/workflows/bun-diff.yml (3)
The workflow name is clear, and the triggers are appropriately configured to monitor changes to the lock file in both PR and main branch contexts.
The permissions follow the principle of least privilege, granting only the necessary access levels required for the workflow's functionality.
Let's verify the workflow's prerequisites and integration with other workflows. ✅ Verification successfulWorkflow prerequisites and integration verified successfully The bun-diff workflow is properly integrated with the project:
🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Check if bun.lockb exists and other workflows that might interact with it
echo "Checking for bun.lockb and related workflows..."
# Check if bun.lockb exists
if [ -f "bun.lockb" ]; then
echo "✓ bun.lockb exists"
else
echo "⚠ bun.lockb not found - workflow might not trigger"
fi
# Check for other workflows that might interact with bun.lockb
echo "Related workflows:"
rg -l "bun.lockb" .github/workflows/
Length of output: 314 Script: #!/bin/bash
# Let's check the content of ci.yml to understand how it interacts with bun.lockb
echo "Content of ci.yml workflow:"
cat .github/workflows/ci.yml
# Also check if there are any bun related commands or configurations
echo -e "\nChecking for bun related files:"
fd -g "bun.config.*"
fd -g "bunfig.*"
Length of output: 1541 Script: #!/bin/bash
# Let's check the setup-bun-with-cache action since it's used in CI
echo "Content of setup-bun-with-cache action:"
cat .github/actions/setup-bun-with-cache/action.yml
# Also check for package.json to verify bun scripts
echo -e "\nChecking package.json for bun scripts:"
cat package.json | grep -A 10 '"scripts":'
Length of output: 1093 .github/actions/setup-bun-with-cache/action.yml (1)
The action name, description, and type are clearly defined following GitHub Actions best practices. .github/workflows/release.yml (3)
The workflow triggers are appropriately set up for a release automation workflow, allowing both automated (push to main) and manual execution.
The tag output is properly defined for potential use in downstream jobs.
The steps are well-configured with pinned action versions using commit hashes, which is a security best practice. The use of Let's verify the existence and structure of the referenced config file: ✅ Verification successful✅ Configuration file is present and properly structured The
🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Verify the tagpr config file exists and has required content
if [ -f ".github/tagpr.ini" ]; then
echo "Config file exists"
cat ".github/tagpr.ini"
else
echo "Warning: Missing config file at .github/tagpr.ini"
fi
Length of output: 360 .pre-commit-config.yaml (1)
The current configuration disables several markdown rules:
Consider if all these exclusions are necessary, especially MD023 and MD036 which help maintain consistent formatting. ✅ Verification successfulMD023 and MD036 rules can be safely enabled Based on the verification results, no markdown files were found that violate either MD023 (headings must start at the beginning of the line) or MD036 (emphasis used instead of a heading). In fact, the repository appears to have very few or no markdown files at all. You can safely enable these two rules by removing them from the disabled list: - id: markdownlint-fix
args: [--disable, MD013, MD024, MD033]🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check if the disabled rules are actually needed
# by scanning markdown files for potential violations
# Test: Check for potential violations of MD023 and MD036
echo "Checking for MD023 violations (headings not at start of line):"
rg "^[[:space:]]+#[[:space:]]" -g "*.md"
echo -e "\nChecking for MD036 violations (emphasis instead of headings):"
rg "^[[:space:]]*[\*_]{1,2}[^*_]+[\*_]{1,2}$" -g "*.md"
Length of output: 672 Script: #!/bin/bash
# First, let's find all markdown files in the repository
echo "Finding all markdown files:"
fd -e md
# Then check for MD023 violations in these files
echo -e "\nChecking for MD023 violations (headings not at start of line):"
fd -e md --exec rg -l "^[[:space:]]+#[[:space:]]" {} \;
# Check for MD036 violations (emphasis used instead of headings)
echo -e "\nChecking for MD036 violations (emphasis instead of headings):"
fd -e md --exec rg -l "^[[:space:]]*[\*_]{1,2}[^*_]+[\*_]{1,2}$" {} \;
# Let's also check the content of these files to understand the markdown structure
echo -e "\nListing first few lines of each markdown file:"
fd -e md -x head -n 10 {}
Length of output: 631 .github/workflows/ci.yml (2)
Since Biome is being used for checking, we should verify its configuration: #!/bin/bash
# Description: Verify Biome configuration
echo "Checking Biome configuration..."
# Look for biome.json or other possible config files
fd -t f "biome.json|biome.config.json"
# Check if check:biome script is defined
if [ -f "package.json" ]; then
echo -e "\nBiome related scripts in package.json:"
cat "package.json" | grep -A 2 '"check:biome":'
fi
The implementation looks correct, but let's verify:
✅ Verification successfulLet me gather more information about the Bun setup action since it wasn't shown in the previous output. ✅ Implementation verified and correct Both required components are properly implemented:
🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify the existence of required files and commands
# Test 1: Check if the local action exists
echo "Checking Bun setup action..."
if [ -f ".github/actions/setup-bun-with-cache/action.yml" ]; then
echo "✓ Bun setup action found"
cat ".github/actions/setup-bun-with-cache/action.yml"
else
echo "✗ Bun setup action missing"
fi
# Test 2: Check if the check:astro script is defined
echo -e "\nChecking package.json scripts..."
if [ -f "package.json" ]; then
echo "package.json contents:"
cat "package.json" | grep -A 5 '"scripts":'
else
echo "✗ package.json not found"
fi
Length of output: 721 Script: #!/bin/bash
# Check if the Bun setup action exists and show its contents
if [ -f ".github/actions/setup-bun-with-cache/action.yml" ]; then
echo "✓ Bun setup action found"
cat ".github/actions/setup-bun-with-cache/action.yml"
else
echo "✗ Bun setup action missing"
fi
Length of output: 740 .github/CODE_OF_CONDUCT.md (1)
The document follows the Contributor Covenant v2.0 structure appropriately and provides a solid foundation for community guidelines. Once the contact information and link formatting are addressed, this will be ready to merge. 🧰 Tools🪛 LanguageTool[style] ~32-~32: Try using a synonym here to strengthen your wording. (COMMENT_REMARK) Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Make the contribution much easier and comfortable.
It keeps the code clean and readable.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Since it's a binary file, this action is needed.
|
@coderabbitai review |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.
Actionable comments posted: 7
🧹 Outside diff range and nitpick comments (20)
.github/actions/setup-bun-with-cache/action.yml (3)
8-9: Consider specifying Bun version.While pinning the action to a specific commit is great for security, not specifying a Bun version could lead to inconsistent environments. Consider adding a version input parameter.
- name: 🍞 Setup Bun uses: oven-sh/setup-bun@4bc047ad259df6fc24a6c9b0f9a0cb08cf17fbe5 # v2.0.1 + with: + bun-version: 1.0.25 # Specify your desired version
11-16: Optimize cache configuration.While the current cache setup is functional, consider these improvements for better cache efficiency:
- Use a more specific path to avoid potential conflicts with other package managers
- Add an intermediate restore-key for better cache hits
with: - path: ./node_modules + path: | + ./node_modules + ~/.bun/install/cache key: ${{ runner.os }}-bun-${{ hashFiles('./bun.lockb') }} - restore-keys: ${{ runner.os }}-bun- + restore-keys: | + ${{ runner.os }}-bun-${{ hashFiles('./bun.lockb') }} + ${{ runner.os }}-bun-
18-20: Enhance installation reliability.Consider using these flags with
bun installto improve reliability and reproducibility:- run: bun install + run: bun install --frozen-lockfile --retry 3 shell: bash
--frozen-lockfile: Ensures exact versions from lockfile are installed--retry 3: Retries failed downloads up to 3 times.github/workflows/release.yml (1)
1-29: Consider enhancing the release workflow with additional safety measures.To make the release process more robust, consider adding:
- Pre-release validation steps (e.g., running tests, linting)
- Automated changelog verification
- Post-release notifications (e.g., Slack, Discord)
- Release artifact validation
These additions would help prevent accidental releases with issues and improve the release process visibility.
.github/pr-labeler.yml (4)
1-1: Consider the implications ofalwaysReplace: trueSetting
alwaysReplaceto true will remove any existing labels on PRs, including those added manually or by other automation. Consider setting this tofalseto preserve additional context that might be added through other means.-alwaysReplace: true +alwaysReplace: false
4-23: Consider standardizing the text matching patternsThe text patterns for PR type detection are using checkbox syntax (
- [x]) which tightly couples this configuration to a specific PR template format. Consider using more flexible patterns that can match various forms of the same intent.customLabels: - text: "- [x] 🎉 New Feature" + text: "feat:|feature:|new feature" label: 🎉 New Feature - text: "- [x] 🧰 Bug" + text: "fix:|bug:|bugfix:" label: 🧰 Bug # ... similar changes for other labels
3-27: Consider adding additional common PR categoriesThe current set of labels covers most common scenarios, but consider adding these additional categories:
- Accessibility (♿️)
- Breaking Changes (💥)
- Configuration (⚙️)
- Localization (🌐)
customLabels: # ... existing labels ... + - text: "a11y:|accessibility:" + label: ♿️ Accessibility + - text: "breaking:|BREAKING CHANGE:" + label: 💥 Breaking + - text: "config:|configuration:" + label: ⚙️ Configuration + - text: "i18n:|l10n:|localization:" + label: 🌐 Localization
24-27: Standardize dependency and release label patternsThe patterns for dependencies and releases use different formats from other labels. Consider standardizing these to match the overall pattern:
- - text: "chore(deps): " + - text: "deps:|dependencies:|upgrade:" label: ⛓️ Dependencies - - text: "Release: v" + - text: "release:|version:" label: 🚀 Release.github/ISSUE_TEMPLATE/1-feature-request.yml (3)
1-3: Consider enhancing the labels for better issue categorization.While the current label is descriptive, consider adding additional labels for better organization and filtering:
type: featurestatus: triage-labels: [🎉 New Feature] +labels: [🎉 New Feature, type: feature, status: triage]
10-12: Enhance the placeholder with more detailed examples.Consider providing more structured examples to help users write better feature requests:
placeholder: | - - I want a feature to... - - This behavior should be... + Examples: + - As a mobile user, I want a dark mode feature to reduce eye strain when using the app at night + - The app should automatically detect system theme preferences + - This would improve user experience by...
32-33: Enhance the additional information section with more guidance.Consider providing more specific guidance about what kind of additional information might be helpful:
label: 🗒️ Additional Information - description: Anything else you want to add + description: | + Any additional context that might help us understand your request better: + - Use cases or scenarios + - Screenshots or mockups (if applicable) + - Similar features in other applications.github/ISSUE_TEMPLATE/2-bug-report.yml (4)
1-3: Enhance the template description for better user guidance.The current description "Something doesn't work" is too vague. Consider providing a more detailed description that helps users understand when to use this template.
name: 🧰 Bug Report -description: Something doesn't work +description: Report a bug or unexpected behavior in the application to help us improve labels: [🧰 Bug]
5-12: Add more guidance for bug descriptions.Consider adding a placeholder with an example and expanding the description to help users provide more detailed and actionable bug reports.
attributes: label: ✏️ Describe the Bug - description: A clear and concise description + description: Provide a clear and concise description of what the bug is and what you expected to happen instead + placeholder: | + Example: + - What happened: The save button doesn't respond when clicked + - What I expected: The form should save and show a success message validations: required: true
13-20: Enhance reproduction steps guidance.Add a placeholder with a numbered list format and request environment information to help reproduce the issue more effectively.
attributes: label: 🏭 How to Reproduce the Bug - description: Steps to reproduce the behavior + description: Provide detailed steps to reproduce the bug and information about your environment + placeholder: | + Environment: + - Browser/Device: + - OS: + - App Version: + + Steps: + 1. Go to '...' + 2. Click on '...' + 3. Scroll down to '...' + 4. See error validations: required: true
34-38: Improve guidance for additional information.Enhance the description to suggest specific types of helpful information users might want to include.
attributes: label: 🗒️ Additional Information - description: Anything else you want to add + description: | + Add any other context about the problem here, such as: + - Screenshots or screen recordings + - Error messages or console logs + - Related problems or workarounds you've tried.pre-commit-config.yaml (3)
2-5: Remove the empty line in the autofix commit message.The empty line in the commit message template might lead to inconsistent commit messages. Consider removing it for better consistency.
autofix_commit_msg: | chore(fix): Auto fixes from pre-commit.com hooks - For more information, see https://pre-commit.ci. + For more information, see https://pre-commit.ci.
8-16: Consider adding more security-focused hooks.While
gitleaksis included for secret scanning, consider adding these security-focused hooks:
detect-aws-credentials: Prevents AWS credentials from being committeddetect-private-key: Prevents private keys from being committed- id: check-yaml - id: end-of-file-fixer - id: trailing-whitespace + - id: detect-aws-credentials + - id: detect-private-key
1-49: Consider adding configuration documentation and version management strategy.While the configuration is comprehensive, consider:
- Adding comments to document the purpose of each hook and its configuration
- Establishing a version management strategy (e.g., using version ranges or exact versions)
- Adding a pre-commit configuration for Astro-specific linting since this is an Astro project
Example documentation format:
# Pre-commit configuration for mobicard # Version management strategy: Use exact versions for stability ci: # CI-specific settings for automated fixes and updates autofix_commit_msg: | chore(fix): Auto fixes from pre-commit.com hooks For more information, see https://pre-commit.ci.Consider adding Astro-specific linting:
- repo: local hooks: - id: astro-check name: Astro Check entry: bun run astro check language: system types: [astro] pass_filenames: false.github/workflows/ci.yml (1)
59-60: Consider adding error handling and artifacts for build failures.To improve debugging of build failures, consider:
- Capturing and uploading build output as an artifact
- Adding error handling for the build command
- name: 🛠️ Build Check - run: bun run build + run: | + bun run build 2>&1 | tee build.log + if [ ${PIPESTATUS[0]} -ne 0 ]; then + echo "Build failed. Check the build.log artifact for details." + exit 1 + fi + + - name: Upload Build Log + if: failure() + uses: actions/upload-artifact@v4 + with: + name: build-log + path: build.log.github/CODE_OF_CONDUCT.md (1)
126-130: Fix Markdown link formattingThere are inconsistencies in the link formatting that should be addressed for better maintainability.
-[https://www.contributor-covenant.org/faq]. Translations are available at +[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). - -[https://www.contributor-covenant.org/faq]: https://www.contributor-covenant.org/faq
🛑 Comments failed to post (7)
.github/workflows/bun-diff.yml (1)
17-26:
⚠️ Potential issueFix runner specification and pin action version.
Two issues need attention:
- The runner specification has incorrect capitalization
- The bun-diff-action version should be pinned to a specific commit for security and reproducibility
Apply these fixes:
- runs-on: Ubuntu-Latest + runs-on: ubuntu-latest steps: - name: 🚚 Checkout Repository uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: 🍞 Show the diff - uses: koki-develop/bun-diff-action@v1 + uses: koki-develop/bun-diff-action@b65a6d5a1b2f8d70f9766e947c0f47c9f5e3f058 # v1📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.jobs: bun-diff: runs-on: ubuntu-latest steps: - name: 🚚 Checkout Repository uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2 - name: 🍞 Show the diff uses: koki-develop/bun-diff-action@b65a6d5a1b2f8d70f9766e947c0f47c9f5e3f058 # v1.github/workflows/release.yml (1)
15-15:
⚠️ Potential issueFix case sensitivity in runner OS name.
The runner OS name should be
ubuntu-latest(lowercase) instead ofUbuntu-Latest. While GitHub Actions is currently case-insensitive, it's best to use the canonical lowercase form for consistency and future compatibility.- runs-on: Ubuntu-Latest + runs-on: ubuntu-latest📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.runs-on: ubuntu-latest.github/ISSUE_TEMPLATE/1-feature-request.yml (1)
22-26: 🛠️ Refactor suggestion
Use relative links and consider making version check required.
Two suggestions for improvement:
- Use relative links to ensure compatibility with forks
- Consider making the version check required to reduce duplicate reports
- - label: I searched the GitHub [Issues](https://github.com/5ouma/mobicard/issues) or [Discussions](https://github.com/5ouma/mobicard/discussions). + - label: I searched the GitHub [Issues](/issues) or [Discussions](/discussions). required: true - label: I tried with the latest version. - required: false + required: true📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.- label: I searched the GitHub [Issues](/issues) or [Discussions](/discussions). required: true - label: I tried with the latest version. required: true - label: I agree to follow the [Code of Conduct](https://github.com/5ouma/mobicard/blob/main/.github/CODE_OF_CONDUCT.md)..github/ISSUE_TEMPLATE/2-bug-report.yml (1)
21-32: 🛠️ Refactor suggestion
Strengthen the confirmation checks.
Consider making the "latest version" check required to reduce duplicate reports of already-fixed issues. Also, use absolute URLs for better reliability.
options: - - label: I searched the GitHub [Issues](https://github.com/5ouma/mobicard/issues) or [Discussions](https://github.com/5ouma/mobicard/discussions). + - label: I have searched existing issues and discussions to ensure this bug hasn't already been reported. required: true - label: I tried with the latest version. - required: false + required: true - label: I agree to follow the [Code of Conduct](https://github.com/5ouma/mobicard/blob/main/.github/CODE_OF_CONDUCT.md). required: true📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.- type: checkboxes id: checks attributes: label: ✔︎ Confirm these checks description: Make sure you reviewed below options: - label: I have searched existing issues and discussions to ensure this bug hasn't already been reported. required: true - label: I tried with the latest version. required: true - label: I agree to follow the [Code of Conduct](https://github.com/5ouma/mobicard/blob/main/.github/CODE_OF_CONDUCT.md). required: true.github/workflows/ci.yml (2)
22-22:
⚠️ Potential issueFix case sensitivity in
runs-onvalue.The
runs-onvalue should be lowercase. ChangeUbuntu-Latesttoubuntu-latestfor all jobs to follow GitHub Actions conventions.- runs-on: Ubuntu-Latest + runs-on: ubuntu-latestAlso applies to: 36-36, 50-50
7-17: 🛠️ Refactor suggestion
Consider expanding path filters for comprehensive CI coverage.
The current path filters might miss important changes in configuration files that could affect the build. Consider adding:
package.json- For dependency changesastro.config.mjsorastro.config.ts- For Astro configuration changestsconfig.json- For TypeScript configuration changespaths: - "**.astro" - "**.ts" - bun.lockb + - package.json + - astro.config.{mjs,ts} + - tsconfig.json - .github/workflows/ci.yml📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.paths: - "**.astro" - "**.ts" - bun.lockb - package.json - astro.config.{mjs,ts} - tsconfig.json - .github/workflows/ci.yml pull_request: paths: - "**.astro" - "**.ts" - bun.lockb - package.json - astro.config.{mjs,ts} - tsconfig.json - .github/workflows/ci.yml.github/CODE_OF_CONDUCT.md (1)
61-63:
⚠️ Potential issueSpecify clear contact methods for reporting incidents
The current contact information "any ways @5ouma have" is too vague and may create uncertainty for community members needing to report incidents. Consider providing specific contact methods.
-reported to the community leaders responsible for enforcement at any ways @5ouma -have. All complaints will be reviewed and investigated promptly and fairly. +reported to the community leaders responsible for enforcement through the following +channels: + +- Email: [specify email] +- GitHub Issues: Create a confidential issue with the 'Code of Conduct' label +- Discord: Direct message to moderators (if applicable) + +All complaints will be reviewed and investigated promptly and fairly.Committable suggestion skipped: line range outside the PR's diff.
<!-- Release notes generated using configuration in .github/release.yml at main --> * Add bio component by @5ouma in #5 * Add homepage component by @5ouma in #7 * Add contact component by @5ouma in #9 * Add index page and default layout template by @5ouma in #13 * Astro requires in-file CSS for scoping by @5ouma in #6 * Add README and license by @5ouma in #11 * Exclude Astro and Astrobook related by @5ouma in #8 * Add more test cases for anomalous conditions by @5ouma in #10 * Allow commenting on commits by @5ouma in #3 * Deploy and analyze performance by @5ouma in #12 * Quote meta file variable by @5ouma in #14 * Change the environment variable for repository name by @5ouma in #15 * Don't treat the input as JSON by @5ouma in #16 * chore(deps): pin koki-develop/bun-diff-action action to 22bcd25 by @renovate in #4 * @5ouma made their first contribution in #1 * @renovate made their first contribution in #4 * @github-actions made their first contribution in #2 **Full Changelog**: https://github.com/5ouma/mobicard/commits/v0.1.0
<!-- Release notes generated using configuration in .github/release.yml at main --> * Add bio component by @5ouma in #5 * Add homepage component by @5ouma in #7 * Add contact component by @5ouma in #9 * Add index page and default layout template by @5ouma in #13 * Astro requires in-file CSS for scoping by @5ouma in #6 * Add README and license by @5ouma in #11 * Exclude Astro and Astrobook related by @5ouma in #8 * Add more test cases for anomalous conditions by @5ouma in #10 * Allow commenting on commits by @5ouma in #3 * Deploy and analyze performance by @5ouma in #12 * Quote meta file variable by @5ouma in #14 * Change the environment variable for repository name by @5ouma in #15 * Don't treat the input as JSON by @5ouma in #16 * chore(deps): pin koki-develop/bun-diff-action action to 22bcd25 by @renovate in #4 * @5ouma made their first contribution in #1 * @renovate made their first contribution in #4 * @github-actions made their first contribution in #2 **Full Changelog**: https://github.com/5ouma/mobicard/commits/v0.1.0
<!-- Release notes generated using configuration in .github/release.yml at main --> * Add bio component by @5ouma in #5 * Add homepage component by @5ouma in #7 * Add contact component by @5ouma in #9 * Add index page and default layout template by @5ouma in #13 * Astro requires in-file CSS for scoping by @5ouma in #6 * Add README and license by @5ouma in #11 * Exclude Astro and Astrobook related by @5ouma in #8 * Add more test cases for anomalous conditions by @5ouma in #10 * Allow commenting on commits by @5ouma in #3 * Deploy and analyze performance by @5ouma in #12 * Quote meta file variable by @5ouma in #14 * Change the environment variable for repository name by @5ouma in #15 * Don't treat the input as JSON by @5ouma in #16 * chore(deps): pin koki-develop/bun-diff-action action to 22bcd25 by @renovate in #4 * @5ouma made their first contribution in #1 * @renovate made their first contribution in #4 * @github-actions made their first contribution in #2 **Full Changelog**: https://github.com/5ouma/mobicard/commits/v0.1.0
