update: more code additons, mainly admin stuff #93

NeonGamerBot-QK · 2025-11-13T18:32:33Z

No description provided.

coolify-hackclub · 2025-11-13T18:32:37Z

The preview deployment is ready. 🟢

Last updated at: 2025-11-16 08:50:06 CET

…, and user impersonation UI/UX Improvements: - Make JSON field monospace on shop item form - Redirect to shop items list after creating new item - Restore auto-calculation of ticket price based on USD cost - Consolidate all admin CSS into admin.scss - Add borders to .card and .table-data classes Warehouse Order Fixes (High Priority): - Fix quantity bug: treat agh_contents as per-unit spec, multiply by order quantity - Add per_unit_contents() and contents_for_order_qty() to WarehouseItem - Add warehouse_pick_lines() to ShopOrder for individual orders - Add combined_pick_lines_for_package() for batched orders - Create PackageBuilder service for batching warehouse orders Blazer Audit Log Protection: - Add database triggers to prevent UPDATE/DELETE on blazer_audits table - Create Blazer::Audit model with immutability callbacks - Remove updated_at column from blazer_audits (audits should never update) User Impersonation: - Add impersonate action for admins to view site as another user - Add stop_impersonating action with session validation - Display prominent red impersonation banner with animations - Log all impersonation starts/ends in PaperTrail audit log - Show impersonation events in user action history - Add helper methods: impersonating?, original_admin Admin Action History: - Display all actions performed on a user (flipper toggles, impersonation, etc.) - Show feature names in flipper events (fixed symbol/string key handling) - Link action history to full audit logs - Add link to admin names in audit log tables

…h audit logging - Add approve, reject, place_on_hold, release_from_hold actions to ShopOrdersController - Manual PaperTrail logging with whodunnit and state transitions - Compact horizontal grid layout for order details (Status, Created, User, Item, Qty/Cost) - Reject modal form with reason input - Vertical audit log showing who made changes, old/new status, rejection reasons - Exclude frozen_address from audit log for privacy - Add btn-danger CSS styling - Add faker gem for shop order seeding - Seed shop orders with 10-20 randomized orders in various states Amp-Thread-ID: https://ampcode.com/threads/T-fe30d0ef-c2a9-4428-b52e-c683f94c5ef0 Co-authored-by: Amp <[email protected]>

coolify-hackclub · 2025-11-17T05:15:23Z

The preview deployment is ready. 🟢

Open Preview | Open Build Logs

Last updated at: 2025-11-17 05:19:40 CET

… admin buttons)

…nto neon-admin-stuff

- Implemented region filtering for shop orders based on user roles. - Added mass reject orders feature in the UsersController. - Updated views to support new region selection and order rejection UI. - Added region column to users table with migration.

app/controllers/shop_controller.rb

Co-authored-by: Copilot <[email protected]>

sentry · 2025-11-25T02:08:00Z

app/controllers/admin/shop_orders_controller.rb

    case params[:sort]
    when "id_asc"


Bug: Calling .order() on an Array after to_a.select converts an ActiveRecord relation to an Array.
_{Severity: CRITICAL | Confidence: High}

🔍 Detailed Analysis

When params[:region] is present, the orders ActiveRecord relation is converted to a Ruby Array by to_a.select on lines 67-76. Subsequently, on lines 79-91, the code attempts to call the .order() method on this Array, which does not possess this method, leading to a NoMethodError and an application crash.

💡 Suggested Fix

Ensure orders remains an ActiveRecord relation before calling .order(). Apply sorting before converting to an Array or implement array-based sorting.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/controllers/admin/shop_orders_controller.rb#L79-L80 Potential issue: When `params[:region]` is present, the `orders` ActiveRecord relation is converted to a Ruby `Array` by `to_a.select` on lines 67-76. Subsequently, on lines 79-91, the code attempts to call the `.order()` method on this `Array`, which does not possess this method, leading to a `NoMethodError` and an application crash.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:02Z

app/views/layouts/application.html.erb

+  <body class="<%= current_user.present? ? 'signed-in' : '' %>"
    <% if current_user.present? %>
      <%= render "shared/sidebar" %>
    <% end %>
-    <main>
      <%= render "shared/flash" %>
-      <%= yield %>
-    </main>
+      <%= yield %>>


Syntax error: The closing <main> tag is missing. Line 43 has an extra > character at the end of <%= yield %>> and the <main> tag is opened on line 42 but never closed. This will break the HTML structure of all pages.
_{Severity: CRITICAL}

💡 Suggested Fix

Suggested change

<body class="<%= current_user.present? ? 'signed-in' : '' %>"

<% if current_user.present? %>

<%= render "shared/sidebar" %>

<% end %>

<main>

<%= render "shared/flash" %>

<%= yield %>

</main>

<%= yield %>>

<body class="<%= current_user.present? ? 'signed-in' : '' %>">

<% if current_user.present? %>

<%= render "shared/sidebar" %>

<% end %>

<main>

<%= render "shared/flash" %>

<%= yield %>

</main>

</body>

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:04Z

app/controllers/shop_controller.rb

+
+    # Create the order
+    # This is a simplified version. In a real app, you'd want to:
+    # 1. Check stock
+    # 2. Check balance/charge user
+    # 3. Handle different item types
+
+    @order = current_user.shop_orders.new(
+        shop_item: @shop_item,
+        quantity: quantity,
+      # Assuming address is stored as json in user model now, but for order history we might want to snapshot it
+      # For now just getting it to save
+    )
+
+    # Set initial state if using AASM
+    if @shop_item.is_a?(ShopItem::FreeStickers)
+        @order.aasm_state = "fulfilled"
+        @order.fulfilled_at = Time.current
+    elsif @order.respond_to?(:aasm_state=)
+        @order.aasm_state = "pending"
+    end
+
+    if @order.save
+        @order.mark_stickers_received if @shop_item.is_a?(ShopItem::FreeStickers)
+        redirect_to shop_my_orders_path, notice: "Order placed successfully!"


The create_order method does not set the frozen_address before saving, but ShopOrder has a check_regional_availability validation that depends on it. This will cause all non-FreeStickers orders to fail validation. The address should be set from current_user.address before validation runs.
_{Severity: HIGH}

💡 Suggested Fix

Suggested change

# Create the order

# This is a simplified version. In a real app, you'd want to:

# 1. Check stock

# 2. Check balance/charge user

# 3. Handle different item types

@order = current_user.shop_orders.new(

shop_item: @shop_item,

quantity: quantity,

# Assuming address is stored as json in user model now, but for order history we might want to snapshot it

# For now just getting it to save

)

# Set initial state if using AASM

if @shop_item.is_a?(ShopItem::FreeStickers)

@order.aasm_state = "fulfilled"

@order.fulfilled_at = Time.current

elsif @order.respond_to?(:aasm_state=)

@order.aasm_state = "pending"

end

if @order.save

@order.mark_stickers_received if @shop_item.is_a?(ShopItem::FreeStickers)

redirect_to shop_my_orders_path, notice: "Order placed successfully!"

@order = current_user.shop_orders.new(

shop_item: @shop_item,

quantity: quantity,

frozen_address: current_user.address

)

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

app/models/shop_order.rb

sentry · 2025-11-25T02:08:10Z

app/javascript/controllers/dropdown_controller.js

+  }
+
+  getPriceRange(range) {
+    if (range.includes("$0")) return [0, 100000];
+    if (range.includes("$100,000 - $500,000")) return [100000, 500000];
+    if (range.includes(">$500,000")) return [500000, Infinity];


The getPriceRange method is checking for string patterns like '$0' and '$100,000', but the shop now uses '🍪' (cookie emoji) as currency in the UI. The price range strings in the dropdown have been updated to use '🍪0 - 🍪1000' format, but this extraction logic hasn't been updated to match. The filtering will fail because the patterns won't match.
_{Severity: HIGH}

💡 Suggested Fix

Suggested change

}

getPriceRange(range) {

if (range.includes("$0")) return [0, 100000];

if (range.includes("$100,000 - $500,000")) return [100000, 500000];

if (range.includes(">$500,000")) return [500000, Infinity];

getPriceRange(range) {

if (range.includes("🍪0")) return [0, 1000];

if (range.includes("🍪1000 - 🍪5000")) return [1000, 5000];

if (range.includes(">🍪5000")) return [5000, Infinity];

return [0, Infinity];

}

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:12Z

app/javascript/controllers/dropdown_controller.js

+    const items = document.querySelectorAll(".shop-item-card");
+    items.forEach((item) => {
+      if (category === "Grants") {
+        item.style.display = "flex";
+      } else if (category === "Warehouse") {
+        item.style.display = "flex";
+      } else if (category === "Third Party") {
+        item.style.display = "flex";
+      }
+    });
+  }


The filterByCategory method shows all items for any category selection (Grants, Warehouse, Third Party). This doesn't actually filter anything - all branches set item.style.display = 'flex'. This functionality needs to be implemented to filter items by their type based on the selected category.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/javascript/controllers/dropdown_controller.js#L28-L38 Potential issue: The `filterByCategory` method shows all items for any category selection (Grants, Warehouse, Third Party). This doesn't actually filter anything - all branches set `item.style.display = 'flex'`. This functionality needs to be implemented to filter items by their type based on the selected category.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:14Z

app/models/user.rb

+  def address
+    {
+      name: display_name,
+      street1: "15 Falls Rd",
+      street2: nil,
+      city: "Shelburne",
+      state: "VT",
+      zip: "05482",
+      country: "US",
+      email: email


The address method returns a hardcoded address in Vermont instead of using the user's actual address from the identity provider. This will cause all orders to be frozen with the same address. The address should either be stored in the User model during login, or retrieved from the User::Identity.
_{Severity: HIGH}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/models/user.rb#L107-L116 Potential issue: The `address` method returns a hardcoded address in Vermont instead of using the user's actual address from the identity provider. This will cause all orders to be frozen with the same address. The address should either be stored in the User model during login, or retrieved from the User::Identity.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:17Z

app/views/admin/shop_items/_form.html.erb

          <div class="mb-3">
            <%= f.label :image, class: "form-label" %>
-            <%= f.file_field :image, class: "form-control" %>
+            <%= f.file_field :image, class: "form-control", required: !shop_item.persisted? %>


The image field has required: !shop_item.persisted? which means it's required on create but not on update. However, the model validates :image, presence: true, on: :create. This is inconsistent - if updates also shouldn't require an image, the validation should allow null on update. If updates should allow skipping the image, consider what happens to orders if the image is removed.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/views/admin/shop_items/_form.html.erb#L41 Potential issue: The image field has `required: !shop_item.persisted?` which means it's required on create but not on update. However, the model validates `:image, presence: true, on: :create`. This is inconsistent - if updates also shouldn't require an image, the validation should allow null on update. If updates should allow skipping the image, consider what happens to orders if the image is removed.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:19Z

app/controllers/admin/shop_orders_controller.rb

+    # Apply region filter after stats calculation (converts to array)
+    if current_user.fulfillment_person? && !current_user.admin? && current_user.region.present?
+      orders = orders.to_a.select do |order|
+        if order.frozen_address.present?
+          order_region = Shop::Regionalizable.country_to_region(order.frozen_address["country"])
+          order_region == current_user.region
+        else
+          false
+        end
+      end
+    elsif params[:region].present?
+      orders = orders.to_a.select do |order|
+        if order.frozen_address.present?
+          order_region = Shop::Regionalizable.country_to_region(order.frozen_address["country"])
+          order_region == params[:region].upcase
+        else
+          false
+        end


In the index method, when a fulfillment person with a region is filtering orders, the code converts the entire orders query to an array with .to_a.select. This loads all orders into memory and then filters them client-side, which is very inefficient for large datasets. This should be done at the database level using a scope or SQL join.
_{Severity: HIGH}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/controllers/admin/shop_orders_controller.rb#L57-L74 Potential issue: In the `index` method, when a fulfillment person with a region is filtering orders, the code converts the entire orders query to an array with `.to_a.select`. This loads all orders into memory and then filters them client-side, which is very inefficient for large datasets. This should be done at the database level using a scope or SQL join.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:21Z

app/controllers/admin/shop_orders_controller.rb

+      authorize :admin, :access_fulfillment_view?
+    else
+      authorize :admin, :access_shop_orders?
+    end
    @order = ShopOrder.find(params[:id])
    @can_view_address = @order.can_view_address?(current_user)
+
+    # Load user's order history for fraud dept


The manual PaperTrail version creation in approve, reject, place_on_hold, release_from_hold, and mark_fulfilled methods duplicates logic that should be handled by PaperTrail automatically via has_paper_trail. The AASM state transitions should already be tracked. Consider removing these manual version creations and letting PaperTrail handle it, or add a consistent callback across all state changes.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/controllers/admin/shop_orders_controller.rb#L112-L119 Potential issue: The manual PaperTrail version creation in `approve`, `reject`, `place_on_hold`, `release_from_hold`, and `mark_fulfilled` methods duplicates logic that should be handled by PaperTrail automatically via `has_paper_trail`. The AASM state transitions should already be tracked. Consider removing these manual version creations and letting PaperTrail handle it, or add a consistent callback across all state changes.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:23Z

app/components/dropdown_component.html.erb

+<div class="<%= dropdown_classes %>" data-controller="dropdown">
  <div class="dropdown__label"><%= label %></div>
-  <button class="dropdown__button">
-    <span class="dropdown__selected">
+  <button class="dropdown__button" data-action="click->dropdown#toggle" data-dropdown-target="button">
+    <span class="dropdown__selected" data-dropdown-target="selected">
      <%= selected_option %>
    </span>
    <%= helpers.inline_svg_tag "icons/chevron-down.svg", class: "dropdown__icon" %>
  </button>
-  <ul class="dropdown__menu">
+  <ul class="dropdown__menu" data-dropdown-target="menu">
    <% options.each do |option| %>
-      <li class="dropdown__item"><%= option %></li>
+      <li class="dropdown__item" data-action="click->dropdown#select"><%= option %></li>
    <% end %>
  </ul>
 </div>


The dropdown component doesn't provide a fallback action for the 'Region' dropdown. Looking at the controller, the Region filter doesn't trigger any JavaScript action, it relies on form submission. However, the Stimulus controller's select method only triggers actions for Category, Price Range, and Sort by. Region changes won't work without adding form submission logic or updating the controller.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/components/dropdown_component.html.erb#L1-L14 Potential issue: The dropdown component doesn't provide a fallback action for the 'Region' dropdown. Looking at the controller, the Region filter doesn't trigger any JavaScript action, it relies on form submission. However, the Stimulus controller's `select` method only triggers actions for Category, Price Range, and Sort by. Region changes won't work without adding form submission logic or updating the controller.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:25Z

app/views/admin/shop_orders/_filters.html.erb

+      <% unless current_user.fulfillment_person? %>
+      <div>
+        <%= f.label :region, "Region" %>
+        <%= f.select :region, options_for_select([
+            ['All regions', ''],
+            ['United States', 'US'],
+            ['EU + UK', 'EU'],
+            ['India', 'IN'],
+            ['Canada', 'CA'],
+            ['Australia & NZ', 'AU'],
+            ['Rest of World', 'XX']
+          ], params[:region]), {}, { class: "form-control" } %>
+      </div>
+      <% end %>
+<% unless current_user.fulfillment_person? %>


The Region filter is only shown to non-fulfillment users, but fulfillment users actually need to see their region assignment. This creates confusion because fulfillment users can't manually change the region filter, even though their view is filtered by region. The UI/logic should be clarified - either show the filter and explain it's read-only, or provide a way to change their assigned region.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/views/admin/shop_orders/_filters.html.erb#L16-L30 Potential issue: The Region filter is only shown to non-fulfillment users, but fulfillment users actually need to see their region assignment. This creates confusion because fulfillment users can't manually change the region filter, even though their view is filtered by region. The UI/logic should be clarified - either show the filter and explain it's read-only, or provide a way to change their assigned region.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:27Z

app/models/shop_order.rb

    frozen_address
  end

+  def warehouse_pick_lines
+    return [] unless shop_item.is_a?(ShopItem::WarehouseItem)
+    shop_item.contents_for_order_qty(quantity || 1)


The decrypted_address_for method creates a PaperTrail version entry for every address access, which could quickly bloat the versions table. This creates an audit log entry for every admin who views an address. Consider batching these or using a separate audit log table specifically for address accesses to avoid polluting the main versions table.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/models/shop_order.rb#L93-L110 Potential issue: The `decrypted_address_for` method creates a PaperTrail version entry for every address access, which could quickly bloat the versions table. This creates an audit log entry for every admin who views an address. Consider batching these or using a separate audit log table specifically for address accesses to avoid polluting the main versions table.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:29Z

db/seeds/shop_orders.rb

+  if order.save(validate: false)
+    # Randomly assign a state (skip AASM callbacks to avoid payout issues)
+    random_state = states.sample
+    state_name = random_state.to_s
+
+    ShopOrder.where(id: order.id).update_all(aasm_state: state_name)
+
+    # Set timestamp for fulfilled state
+    if random_state == :fulfilled
+      ShopOrder.where(id: order.id).update_all(
+        fulfilled_at: Time.current,
+        fulfilled_by: "SEED",


The seed script uses order.save(validate: false) to bypass validations, then directly updates the aasm_state without using AASM events. This creates orders that don't properly trigger callbacks or state transition logic. For testing purposes, either ensure validations pass naturally, or document why they're being bypassed.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: db/seeds/shop_orders.rb#L51-L62 Potential issue: The seed script uses `order.save(validate: false)` to bypass validations, then directly updates the aasm_state without using AASM events. This creates orders that don't properly trigger callbacks or state transition logic. For testing purposes, either ensure validations pass naturally, or document why they're being bypassed.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

sentry · 2025-11-25T02:08:31Z

app/assets/stylesheets/components/_impersonation.scss

+  }
+}
+


The impersonation banner CSS targets body:has(.impersonation-banner) main to adjust margin, but the application layout now has a broken HTML structure with the missing closing <main> tag. This selector won't work until that's fixed. Additionally, the selector assumes a main element exists as a sibling, which may not be reliable.
_{Severity: MEDIUM}

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not valid. Location: app/assets/stylesheets/components/_impersonation.scss#L93-L95 Potential issue: The impersonation banner CSS targets `body:has(.impersonation-banner) main` to adjust margin, but the application layout now has a broken HTML structure with the missing closing `<main>` tag. This selector won't work until that's fixed. Additionally, the selector assumes a `main` element exists as a sibling, which may not be reliable.

_{Did we get this right? 👍 / 👎 to inform future reviews.}
_{Reference ID: 3348374}

Copilot

Pull request overview

Copilot reviewed 70 out of 73 changed files in this pull request and generated 6 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-11-25T02:09:12Z

app/views/shop/index.html.erb

-      ) %>
+      <% @shop_items.each do |item| %>
+        <% if item.image.present? %>
+          <!-- DEBUG: item.type = <%= item.type %> -->


Potential XSS vulnerability: HTML comment with dynamic content  should be removed from production code. Debug comments can leak sensitive information and should not be present in views.

Copilot · 2025-11-25T02:09:12Z

app/views/kitchen/index.html.erb

  </div>
+
+  <% unless @has_identity_linked %>
+      <%= form_tag "/auth/idv", method: :post, data: {turbo: false} do %>


Missing Turbo configuration. The form at line 39 has data: {turbo: false} but Turbo is part of the Hotwire stack. This attribute should be data: { turbo: "false" } (string value) to properly disable Turbo for this form.

Copilot · 2025-11-25T02:09:12Z

app/controllers/sessions_controller.rb

    return redirect_to(root_path, alert: "Authentication failed") if identity_data.blank?

-    user_email, display_name, verification_status, slack_id, uid = extract_identity_fields(identity_data)
+    user_email, display_name, verification_status, slack_id, uid, = extract_identity_fields(identity_data)


Trailing comma in parameter list. Line 17 has a trailing comma after the uid variable assignment which will cause a syntax error or unexpected behavior. The comma should be removed.

Suggested change

user_email, display_name, verification_status, slack_id, uid, = extract_identity_fields(identity_data)

user_email, display_name, verification_status, slack_id, uid, _address = extract_identity_fields(identity_data)

Copilot · 2025-11-25T02:09:13Z

app/views/layouts/application.html.erb

+  <body class="<%= current_user.present? ? 'signed-in' : '' %>"
    <% if current_user.present? %>
      <%= render "shared/sidebar" %>
    <% end %>
-    <main>
      <%= render "shared/flash" %>
-      <%= yield %>
-    </main>
+      <%= yield %>>


Syntax error: Missing closing tag for <body>. Line 39 has an incomplete opening tag <body class="<%= current_user.present? ? 'signed-in' : '' %>" without a closing >. Additionally, line 44 has an extra > after <%= yield %> creating <%= yield %>> which will render as text.

Copilot · 2025-11-25T02:09:13Z

db/migrate/20251115000002_add_immutability_to_blazer_audits.rb

+    add_index :blazer_audits, :created_at if index_exists?(:blazer_audits, :created_at)
+  end


Migration rollback issue: In the down method, add_index is called when it should be remove_index. The condition also appears incorrect - it should remove the index if it exists, not add it.

Copilot · 2025-11-25T02:09:13Z

app/assets/stylesheets/pages/shop/_shop.scss

+          color: var(--color-bg);
+          padding: 1em 2em;
+          font-size: 1.5rem;
+          font-family: var(--font-family-text);


Spelling error in comment: "fanily" should be "family" in the font-family property comment.

update: more code additons, mainly admin stuff

2580bee

NeonGamerBot-QK and others added 5 commits November 15, 2025 22:06

feat: enhance user role management and add shop order seeding

c6de0f0

Merge branch 'main' into neon-admin-stuff

066b67a

Merge branch 'main' into neon-admin-stuff

02bbd2d

cskartikey force-pushed the main branch 2 times, most recently from ad4abea to bc5880f Compare November 19, 2025 03:28

cskartikey and others added 4 commits November 19, 2025 21:52

feat: implement sign in w/ IDV

9f019fe

Merge branch 'main' into neon-admin-stuff

cf0f494

fix: #135

1e3dfaf

fix: #128 + db annotations

1e194de

cskartikey force-pushed the main branch from 9f019fe to 8ac30dc Compare November 20, 2025 02:58

NeonGamerBot-QK and others added 12 commits November 20, 2025 19:09

update: shop order rejections + additions + agent.md stuff + lint

66bc483

update: add dark brown buttons flipper (helps keep track of admin/non…

38bbe07

… admin buttons)

Merge branch 'main' into neon-admin-stuff

8c65483

Merge branch 'main' into neon-admin-stuff

2c2d357

before conflicts

3719622

Merge remote-tracking branch 'refs/remotes/origin/neon-admin-stuff' i…

9e94fba

…nto neon-admin-stuff

update: i think we are stable

dc9465c

Add mobile sidebar, make shop responsive and add basic order page (#163)

7268938

update: slight shop fixes

96dd73f

update: shop free stickers focus + customs warning

a3899f0

update: we are ready for the free stickers i think.

23fa8f8

NeonGamerBot-QK self-assigned this Nov 24, 2025

NeonGamerBot-QK requested a review from cskartikey November 24, 2025 04:59

NeonGamerBot-QK added the enhancement New feature or request label Nov 24, 2025

Copilot finished reviewing on behalf of 3kh0 November 24, 2025 18:07

This comment was marked as resolved.

Sign in to view

sentry bot reviewed Nov 24, 2025

View reviewed changes

app/controllers/shop_controller.rb Outdated Show resolved Hide resolved

NeonGamerBot-QK and others added 6 commits November 24, 2025 13:20

Update app/controllers/sessions_controller.rb

4333db6

Co-authored-by: Copilot <[email protected]>

fix the random typo

b3622f3

update agent mistype

a527ccd

only mark it as received on save

96f68d2

linting grr

471bd91

remove dup shop perms

a3b4d4e

3kh0 requested a review from Copilot November 25, 2025 02:05

Copilot started reviewing on behalf of 3kh0 November 25, 2025 02:06 View session

Copilot finished reviewing on behalf of 3kh0 November 25, 2025 02:07

sentry bot reviewed Nov 25, 2025

View reviewed changes

app/models/shop_order.rb Show resolved Hide resolved

sentry bot reviewed Nov 25, 2025

View reviewed changes

Copilot AI reviewed Nov 25, 2025

View reviewed changes

3kh0 added 2 commits November 24, 2025 21:13

fix unneeded >

1cb712d

mark parts of the user model as todo

965ddfc

	user_email, display_name, verification_status, slack_id, uid, = extract_identity_fields(identity_data)
	user_email, display_name, verification_status, slack_id, uid, _address = extract_identity_fields(identity_data)

		add_index :blazer_audits, :created_at if index_exists?(:blazer_audits, :created_at)
		end

update: more code additons, mainly admin stuff #93

Are you sure you want to change the base?

update: more code additons, mainly admin stuff #93

Uh oh!

Conversation

NeonGamerBot-QK commented Nov 13, 2025

Uh oh!

coolify-hackclub bot commented Nov 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coolify-hackclub bot commented Nov 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

sentry bot Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

coolify-hackclub bot commented Nov 13, 2025 •

edited

Loading

coolify-hackclub bot commented Nov 17, 2025 •

edited

Loading