On November 1st, OpenAI officially launched ChatGPT Search. After using it for one day, I must say I can’t live without it. Here is an introduction to this excellent feature.
When submitting a Merge Request (MR) for a project branch, there are three options: Merge, Rebase, and Squash.
What are the differences between these three options, and how should you choose? Here’s a summary.
The essence of Merge is creating a new commit node, with all commits from the source branch brought over. If there were initially three commits, after the Merge, four commit nodes will exist, with one being the Merge Commit. The commit created by Merge also carries the source branch’s commit information. Therefore, in many Git GUI tools, these details form a commit relationship graph.
I learned about the tag’s custom target attribute during the technical weekly meeting, and here is my note.
HTML target
Where to display the linked URL as the name for a browsing context (a tab, window, or <iframe>). The following keywords have special meanings for where to load the URL: _self, _blank, _parent, _top.
When accessing the web page in Chrome, everything is normal, but the page crashes directly when the developer tools are opened. If the page is refreshed with the developer tools open, it crashes but usually loads and runs when the developer tools are closed.
Version: Chrome v130.0.6723.70. Version v129 usually works.
In projects, we often use many third-party NPM packages, such as Mousetrap. We usually encounter bugs that have not yet been fixed or merged by the official repository. So, what should we do in such cases? Here is a summary of the methods.
You can fork the repository, modify the source code, submit a PR, and wait for the official team to merge and release a new package. This method is undoubtedly the best; it benefits and gives back to the community.
However, this approach’s downside is also quite noticeable. If the official longed and we urgently need the package, this solution may not be very suitable.