mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #597] Decide if composer.lock should be tracked in Git (or stay with composer.lock in .gitignore) #418
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#418
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @marclaporte on GitHub (Aug 14, 2022).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/597
https://stackoverflow.com/questions/12896780/should-composer-lock-be-committed-to-version-control
https://search.brave.com/search?q=composer.lock
composer.lock is now in https://github.com/jasonmunro/cypht/blob/master/.gitignore
Related: https://github.com/jasonmunro/cypht/issues/311
@marclaporte commented on GitHub (Aug 22, 2022):
Related chat thread on Gitter: https://gitter.im/cypht-org/community?at=62fa629511a6a83d040e77fb
@Tea23 commented on GitHub (Sep 26, 2022):
Removing composer.lock has caused an issue with install. As composer.json contains the pre install and pre update commands
composer check-platform-reqs,composer installexpects a lockfile to be present.I'm a neophyte with composer and stuff, so I worked around this by replacing the commands in pre-install and pre-update with
echo hiand thencomposer installcorrectly generated the lockfile.@kk6mrp commented on GitHub (Oct 1, 2022):
I'm having this same issue when trying to update.
@marclaporte commented on GitHub (Nov 1, 2022):
Related: https://github.com/jasonmunro/cypht/pull/632/files
@marclaporte commented on GitHub (Jul 7, 2023):
For the record, composer.lock was removed here:
github.com/cypht-org/cypht@131daacbebAnd it's highly likely we will resume maintaining composer.lock in Git
@marclaporte commented on GitHub (Jul 11, 2023):
composer.lock is now back in the code base:
github.com/cypht-org/cypht@58f007a324