You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally, the icds-pages-data.json was added as part of an internal issue #349 , where it is kept in the public directory so it can be accessed via an endpoint on our site. However, this file has contributed to countless merge conflict issues due to it formatting certain things differently on people's machines, only to then be pushed up when updates are made to page content.
💬 Description
Is it possible to remove the file from source control, and have it perhaps generated on the CI and served up to users on the live site? Am aware it is used by the component gallery, however should still be possible to generate a local copy for testing, and having the deployed version use the copy held in the public directory.
Why do we need it?
Would prevent future merge conflicts from occurring when there are no actual clashes between changes, speeding up productivity and also reducing space taken by files in our repository.
The text was updated successfully, but these errors were encountered:
GCHQ-Developer-741
changed the title
Prevent icds-pages-data.json from being committed to GitHub
Remove icds-pages-data.json from source control
Dec 3, 2024
Summary
Originally, the
icds-pages-data.json
was added as part of an internal issue #349 , where it is kept in the public directory so it can be accessed via an endpoint on our site. However, this file has contributed to countless merge conflict issues due to it formatting certain things differently on people's machines, only to then be pushed up when updates are made to page content.💬 Description
Is it possible to remove the file from source control, and have it perhaps generated on the CI and served up to users on the live site? Am aware it is used by the component gallery, however should still be possible to generate a local copy for testing, and having the deployed version use the copy held in the public directory.
Why do we need it?
Would prevent future merge conflicts from occurring when there are no actual clashes between changes, speeding up productivity and also reducing space taken by files in our repository.
The text was updated successfully, but these errors were encountered: