Problem/Motivation

Since the 2573b638 commit in September removed 5 .DS_Store files, I thought I should mention that I found 3 more:

  • ./config/.DS_Store
  • ./css/.DS_Store
  • ./subtheme/config/.DS_Store

Issue fork bootstrap_barrio-3492730

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

kwiseman created an issue. See original summary.

kwiseman opened merge request !88

kwiseman’s picture

kwiseman commented
Status: Active » Needs review
clarkssquared’s picture

clarkssquared commented
Status: Needs review » Reviewed & tested by the community

Hi kwiseman,

The MR is pretty straight forward as it removes the .DS_Store files as per the report, I applied it and I confirmed that there are no .DS_Store files anywhere in the theme's directory

➜  bootstrap_barrio git:(5.5.x) find . -name .DS_Store
./subtheme/config/.DS_Store
./css/.DS_Store
./config/.DS_Store
➜  bootstrap_barrio git:(5.5.x) curl https://git.drupalcode.org/project/bootstrap_barrio/-/merge_requests/88.diff | git apply -v
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   666    0   666    0     0   1070      0 --:--:-- --:--:-- --:--:--  1081
Checking patch config/.DS_Store...
Checking patch css/.DS_Store...
Checking patch subtheme/config/.DS_Store...
Applied patch config/.DS_Store cleanly.
Applied patch css/.DS_Store cleanly.
Applied patch subtheme/config/.DS_Store cleanly.
➜  bootstrap_barrio git:(5.5.x) ✗ find . -name .DS_Store
➜  bootstrap_barrio git:(5.5.x) ✗

hatuhay made their first commit to this issue’s fork.

hatuhay’s picture

hatuhay commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.