Fixes profile page with removal of init date

[github-actions[bot]]

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

1. 👀 Observe the CI jobs and tests to ensure they are passing

2. ✔️ Obtain an approval/review on this pull request

3. 🚀 Deploy your pull request to the development environment with .deploy to development

4. 🚀 Deploy your pull request to the production environment with .deploy

   If anything goes wrong, rollback with .deploy main

5. 🎉 Merge!

Note: If you have a larger change and want to block deployments, you can run .lock --reason <reason> to lock all other deployments (remove with .unlock)

You can view the branch deploy usage guide for additional information

[Blightbuster]

.deploy to development

[github-actions[bot]]

⚠️ Cannot claim deployment lock

Sorry Blightbuster, the development environment deployment lock is currently claimed by Razzmatazzz

Lock Details 🔒

• Environment: development
• Branch: 9ca6b94c352bc53fd4200fcd25c35301d95b0301
• Created At: 2024-04-09T20:30:04.137Z
• Created By: Razzmatazzz
• Sticky: true
• Global: false
• Comment Link: click here
• Lock Link: click here

The current lock has been active for 16d:7h:7m:36s

If you need to release the lock, please comment .unlock development

[Blightbuster]

.unlock development

[Blightbuster]

.deploy to development

[github-actions[bot]]

🔓 Deployment Lock Removed

The development deployment lock has been successfully removed

[github-actions[bot]]

Deployment Triggered 🚀

Blightbuster, started a branch deployment to development

You can watch the progress here 🔗

Branch: fix-profile

[github-actions[bot]]

Deployment Results ✅

Blightbuster successfully deployed branch fix-profile to development

Show Results

https://f3f9e2ad.tarkov-dev.pages.dev

[Blightbuster]

.help

[github-actions[bot]]

📚 Branch Deployment Help

This help message was automatically generated based on the inputs provided to this Action.

💻 Available Commands

• .help - Show this help message
• .deploy - Deploy this branch to the production environment
• .deploy main - Rollback the production environment to the main branch
• .noop - Deploy this branch to the production environment in noop mode
• .lock - Obtain the deployment lock (will persist until the lock is released)
• .lock --reason <text> - Obtain the deployment lock with a reason (will persist until the lock is released)
• .lock <environment> - Obtain the deployment lock for the specified environment (will persist until the lock is released)
• .lock <environment> --reason <text> - Obtain the deployment lock for the specified environment with a reason (will persist until the lock is released)
• .lock --global - Obtain a global deployment lock (will persist until the lock is released) - Blocks all environments
• .lock --global --reason <text> - Obtain a global deployment lock with a reason (will persist until the lock is released) - Blocks all environments
• .unlock - Release the deployment lock (if one exists)
• .unlock <environment> - Release the deployment lock for the specified environment (if one exists)
• .unlock --global - Release the global deployment lock (if one exists)
• .lock --details - Show information about the current deployment lock (if one exists)
• .lock <environment> --details - Get information about the current deployment lock for the specified environment (if one exists)
• .lock --global --details - Show information about the current global deployment lock (if one exists)
• .wcid - Alias for .lock --details

🌍 Environments

These are the available environments for this Action as defined by the inputs provided to this Action.

Note: Just because an environment is listed here does not mean it is available for deployment

• production - The default environment for this Action
• production - The environments that are considered "production"
• production,development - The list of environments that can be targeted for deployment

🔭 Example Commands

The following set of examples use this Action's inputs to show you how to use the commands.

• .deploy - Deploy this branch to the production environment
• .deploy main - Rollback the production environment to the main branch
• .noop - Deploy this branch to the production environment in noop mode
• .deploy to <production|development> - Deploy this branch to the specified environment (note: the to keyword is optional)
• .lock <production|development> - Obtain the deployment lock for the specified environment
• .unlock <production|development> - Release the deployment lock for the specified environment
• .lock <production|development> --details - Get information about the deployment lock for the specified environment

⚙️ Configuration

The following configuration options have been defined for this Action:

• reaction: eyes - The GitHub reaction icon to add to the deployment comment when a deployment is triggered
• update_branch: warn - This Action will warn if the branch is out of date with the base branch
• outdated_mode: strict
• required_contexts: false - There are no designated required contexts for this Action (default and suggested)
• allowForks: true - This Action will not run on forked repositories
• skipCi: development - This Action will not require passing CI for the environments specified
• checks: all - All CI checks must pass before a deployment can be requested
• skipReviews: development - This Action will not require passing reviews for the environments specified
• draft_permitted_targets: false - This Action will not draft pull requests to be deployed to any environment
• admins: the-hideout/core-contributors - This Action will allow the listed admins to bypass pull request reviews before deployment
• permissions: write,maintain,admin - The acceptable permissions that this Action will require to run
• allow_sha_deployments: false - This Action will not allow deployments to an exact SHA (recommended)

---

View the full usage guide here for additional help

[Blightbuster]

.deploy

[github-actions[bot]]

Deployment Triggered 🚀

Blightbuster, started a branch deployment to production

You can watch the progress here 🔗

Branch: fix-profile

[github-actions[bot]]

Deployment Results ✅

Blightbuster successfully deployed branch fix-profile to production

Environment URL: tarkov.dev

[Blightbuster]

nice